What is CVE-2026-86075?

CVE-2026-86075 is a high-severity allocation of resources without limits or throttling vulnerability in n8n (npm), affecting versions >= 2.38.0, < 2.38.2. It is fixed in 2.38.2, 2.37.7. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.

Which versions of n8n are affected by CVE-2026-86075?

n8n (npm) versions >= 2.38.0, < 2.38.2 is affected.

Is there a fix for CVE-2026-86075?

Yes. CVE-2026-86075 is fixed in 2.38.2, 2.37.7. Upgrade to this version or later.

Is CVE-2026-86075 exploitable, and should I be worried?

Whether CVE-2026-86075 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-86075 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-86075?

Upgrade: n8n to 2.38.2 or later, n8n to 2.37.7 or later.

CVE-2026-86075 in n8n

Q: Which versions of n8n are affected by CVE-2026-86075?

n8n (npm) versions >= 2.38.0, < 2.38.2 is affected.

Q: Is there a fix for CVE-2026-86075?

Yes. CVE-2026-86075 is fixed in 2.38.2, 2.37.7. Upgrade to this version or later.

Q: Is CVE-2026-86075 exploitable, and should I be worried?

Whether CVE-2026-86075 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-86075 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-86075?

Upgrade: n8n to 2.38.2 or later, n8n to 2.37.7 or later.

Summary

n8n: Unauthenticated Persistent Storage Exhaustion via OAuth Dynamic Client Registration Endpoint

Workarounds

If upgrading is not immediately possible, administrators should consider the following temporary mitigations:

Restrict network access to the n8n instance so that only trusted clients can reach it.
Place the instance behind a reverse proxy configured to enforce strict request body size limits below the default 16 MiB.
Monitor database size for unexpected growth and audit the oauth_clients table for anomalous entries.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

Impact

The OAuth Dynamic Client Registration endpoints validated field sizes only for redirect_uris, leaving client_name and grant_types bounded by presence checks alone. An unauthenticated remote caller could submit arbitrarily large values in either field and have them persisted to the database. Repeated registration therefore grew persistent storage without limit and without any account on the instance. The patch caps client_name at its column length and limits grant_types to the grant types the server actually implements, with the array capped at that count.

The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap. Typical impact: resource exhaustion leading to denial of service.

Affected versions

n8n (>= 2.38.0, < 2.38.2) n8n (< 2.37.7)

Security releases

n8n → 2.38.2 (npm) n8n → 2.37.7 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

The issue has been fixed in n8n versions 2.37.7 and 2.38.2. Users should upgrade to one of these versions or later to remediate the vulnerability.

Frequently Asked Questions

What is CVE-2026-86075? CVE-2026-86075 is a high-severity allocation of resources without limits or throttling vulnerability in n8n (npm), affecting versions >= 2.38.0, < 2.38.2. It is fixed in 2.38.2, 2.37.7. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.
Which versions of n8n are affected by CVE-2026-86075? n8n (npm) versions >= 2.38.0, < 2.38.2 is affected.
Is there a fix for CVE-2026-86075? Yes. CVE-2026-86075 is fixed in 2.38.2, 2.37.7. Upgrade to this version or later.
Is CVE-2026-86075 exploitable, and should I be worried? Whether CVE-2026-86075 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-86075 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-86075?
- Upgrade n8n to 2.38.2 or later
- Upgrade n8n to 2.37.7 or later