n8n: Unauthenticated Persistent Storage Exhaustion via OAuth Dynamic Client Registration Endpoint
- Product
- n8n
- CVE
- CVE-2026-86075
- Affected
- npm/n8n < 2.37.7 and >= 2.38.0, < 2.38.2
- Fixed in
- 2.37.7 and 2.38.2
Last verified against sources: October 26, 2026
Am I affected?
n8n: affected npm/n8n < 2.37.7 and >= 2.38.0, < 2.38.2. Fixed in 2.37.7 and 2.38.2.
- Check your version: run
npm ls n8n. Versions >= 2.38.0, < 2.38.2 of n8n are affected. [1]
What to do now
- Upgrade to the fixed version: run
npm install n8n@2.38.2(first patched version 2.38.2). [1] - Upgrade to versions 2.37.7 or 2.38.2 or later. [1]
- Restrict network access to the n8n instance so that only trusted clients can reach it. [1]
- Place the instance behind a reverse proxy configured to enforce strict request body size limits below the default 16 MiB. [1]
- Monitor database size for unexpected growth and audit the oauth_clients table for anomalous entries. [1]
General practice, not from the source: if the affected software could read tokens or credentials, rotate them after upgrading; pin versions and review changes before updating tools your agents run.
What happened
Impact
What was done
Sources
- GHSA-hh89-3r9w-qj3j — GitHub Advisory Database
Every statement above was checked against these sources before publishing. Spotted an error? Tell us and we will correct it with a dated note.
Share advisory brief with your team
Copy a plain-text summary for Slack, GitHub issues, or team security channels.
[CVE-2026-86075] n8n: Unauthenticated Persistent Storage Exhaustion via OAuth Dynamic Client Registration Endpoint
Product: n8n | Affected: npm/n8n < 2.37.7 and >= 2.38.0, < 2.38.2 | Fixed in: 2.37.7 and 2.38.2
Summary: The OAuth Dynamic Client Registration endpoints validated field sizes only for redirect_uris, leaving client_name and grant_types bounded by presence checks alone.
Source & remediation on AgentArmorHQ: https://agentarmorhq.com/incidents/2026/09/cve-2026-86075-n8nCorrections
Report an error or request a correction. We review requests within 5 business days and add a dated correction note.
Discussions for CVE-2026-86075
Ask questions or share configuration tips. Governed by our Community Rules & Terms.
No posts match this filter yet.
Be the first to ask a question or share a working tip.