Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-86075 – Unauthenticated Storage Exhaustion (DoS) – n8n < 2.37.7 and 2.38.0–2.38.1

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-86075 is an unauthenticated denial-of-service vulnerability in n8n’s OAuth Dynamic Client Registration endpoint. Insufficient input validation on the client_name and grant_types fields allows an attacker to submit oversized values that are persisted to the database without any authentication, letting repeated requests exhaust storage. The issue carries a high severity rating due to its network-exploitable, unauthenticated nature.

Technical details

  • Root cause: the OAuth Dynamic Client Registration endpoint validates and bounds redirect_uris, but does not enforce equivalent length/size constraints on client_name or grant_types.
  • Trigger conditions: an attacker submits a client registration request with arbitrarily large client_name and/or grant_types values; the oversized data is written to the database.
  • Attack vector: network, no authentication or user interaction required (the registration endpoint is unauthenticated by design).
  • Impact: repeated abuse of the endpoint causes unbounded growth of the oauth_clients table, exhausting persistent storage and leading to denial of service; confidentiality and integrity are not affected.

Affected software

  • n8n versions prior to 2.37.7
  • n8n versions 2.38.0 through 2.38.1

Severity

  • CVSS score: 8.7 (High)
  • CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: upgrade to n8n 2.37.7 or 2.38.2 (or later), which restrict client_name to database column length limits and cap grant_types to the server’s implemented grant types.
  • If immediate patching is not possible: restrict network access to the OAuth Dynamic Client Registration endpoint, deploy a reverse proxy enforcing a request body size limit (below 16 MiB), and monitor the oauth_clients database table for anomalous growth.

How IONIX identifies potentially affected assets

IONIX matches the following signal against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: n8n.io - Workflow Automation

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge