CVE-2026-86075

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.6% (49th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2026-74281 (ENISA EUVD) · GHSA-hh89-3r9w-qj3j (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

n8n is an open source workflow automation platform. Prior to 2.37.7 and 2.38.2, the OAuth Dynamic Client Registration endpoint bounded redirect_uris but accepted arbitrarily large client_name and grant_types values. An unauthenticated remote caller could repeatedly persist oversized values in oauth_clients and exhaust database storage. The affected validation is in packages/cli/src/modules/oauth-server/oauth-server.service.ts, including MAX_CLIENT_NAME_LENGTH and MAX_GRANT_TYPES. This issue is fixed in versions 2.37.7 and 2.38.2.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
49th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-09). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 8, 2026

Last Modified

September 11, 2026

Advisory Details (3)

Auto-updated Sep 8, 2026
Patch available. Sources: github, github_release.
GitHub release Patch Available

[email protected]

Patch available: n8n-io/n8n [email protected] (pre-release)

https://github.com/n8n-io/n8n/releases/tag/[email protected]
GitHub advisoryMentions a patch (unverified)

Unauthenticated Persistent Storage Exhaustion via OAuth Dynamic Client Registration Endpoint · Advisory · n8n-io/n8n · GitHub

https://github.com/n8n-io/n8n/security/advisories/GHSA-hh89-3r9w-qj3j

Vendor Advisories for CVE-2026-86075(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmn8n @ 2.38.2 (fixes >= 2.38.0, < 2.38.2)—ghsa
npmn8n @ 2.37.7 (fixes < 2.37.7)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
n8n—
  • 2.38.0 up to 2.38.2: fixed in 2.38.2
  • every version up to 2.37.7: fixed in 2.37.7
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 33× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 113 rows on record for this CVE, as 99 entries (1 repeat merged).

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 13 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:57 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  2. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  3. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  4. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  5. 2026-11-09 17:36 UTCEchelonGraph re-scored
  6. 2026-11-09 17:36 UTCGHSA enrichmentGHSA-hh89-3r9w-qj3j · GitHub severity HIGH
  7. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  8. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  9. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  10. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  11. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  12. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  13. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  14. 2026-11-03 05:34 UTCEchelonGraph re-scored
  15. 2026-11-03 05:34 UTCGHSA enrichmentGHSA-hh89-3r9w-qj3j · GitHub severity HIGH
  16. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  17. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  18. 2026-11-01 07:38 UTCGHSA enrichmentGHSA-hh89-3r9w-qj3j · GitHub severity HIGH
  19. 2026-11-01 07:38 UTCEchelonGraph re-scored
  20. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  21. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  22. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  23. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  24. 2026-10-27 17:31 UTCEchelonGraph re-scored
  25. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
Show 74 more
  1. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  2. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  3. 2026-10-25 13:55 UTCEchelonGraph re-scored
  4. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  5. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  6. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  7. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  8. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  9. 2026-10-19 17:27 UTCEchelonGraph re-scored
  10. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  11. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  12. 2026-10-18 03:05 UTCEchelonGraph re-scored
  13. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  14. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  15. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  16. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  17. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  18. 2026-10-13 05:23 UTCEchelonGraph re-scored
  19. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  20. 2026-10-12 14:52 UTCEchelonGraph re-scored
  21. 2026-10-11 19:17 UTCEchelonGraph re-scored
  22. 2026-10-11 16:34 UTCEchelonGraph re-scored
  23. 2026-10-11 13:51 UTCEchelonGraph re-scored
  24. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  25. 2026-10-11 10:28 UTCEchelonGraph re-scored
  26. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  27. 2026-10-09 20:24 UTCEchelonGraph re-scored
  28. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  29. 2026-10-09 00:23 UTCEchelonGraph re-scored
  30. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  31. 2026-10-08 10:16 UTCEchelonGraph re-scored
  32. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  33. 2026-10-06 18:37 UTCEchelonGraph re-scored
  34. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  35. 2026-10-06 05:40 UTCEchelonGraph re-scored
  36. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  37. 2026-10-05 02:23 UTCEchelonGraph re-scored
  38. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  39. 2026-10-04 00:28 UTCEchelonGraph re-scored
  40. 2026-10-02 19:19 UTCEchelonGraph re-scored
  41. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  42. 2026-10-02 06:22 UTCEchelonGraph re-scored
  43. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  44. 2026-09-30 15:09 UTCEchelonGraph re-scored
  45. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  46. 2026-09-30 02:12 UTCEchelonGraph re-scored
  47. 2026-09-29 07:57 UTCEchelonGraph re-scored
  48. 2026-09-28 18:59 UTCEchelonGraph re-scored
  49. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  50. 2026-09-27 17:03 UTCEchelonGraph re-scored
  51. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  52. 2026-09-27 04:06 UTCEchelonGraph re-scored
  53. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  54. 2026-09-26 15:08 UTCEchelonGraph re-scored
  55. 2026-09-24 21:49 UTCEchelonGraph re-scored
  56. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  57. 2026-09-23 19:39 UTCEchelonGraph re-scored
  58. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  59. 2026-09-22 17:13 UTCEchelonGraph re-scored
  60. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  61. 2026-09-22 04:11 UTCEchelonGraph re-scored
  62. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  63. 2026-09-21 02:16 UTCEchelonGraph re-scored
  64. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  65. 2026-09-20 00:06 UTCEchelonGraph re-scored
  66. 2026-09-18 22:11 UTCEchelonGraph re-scored
  67. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  68. 2026-09-17 20:16 UTCEchelonGraph re-scored
  69. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  70. 2026-09-16 15:15 UTCEchelonGraph re-scored
  71. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  72. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  73. 2026-09-15 13:19 UTCEchelonGraph re-scored
  74. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.3% · 27th percentile

Frequently asked(5)

What is CVE-2026-86075?
CVE-2026-86075 is a high-severity vulnerability; its CVE record was published on September 8, 2026. n8n is an open source workflow automation platform. Prior to 2.37.7 and 2.38.2, the OAuth Dynamic Client Registration endpoint bounded redirect_uris but accepted arbitrarily large client_name and grant_types values. An unauthenticated remote caller could repeatedly persist oversized values in…
When was the CVE record for CVE-2026-86075 published?
The CVE record for CVE-2026-86075 was published on September 8, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 11, 2026; the record at its source may have been updated since.
Is CVE-2026-86075 actively exploited?
CVE-2026-86075 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (49th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-86075?
CVE-2026-86075 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-86075?
A fix for CVE-2026-86075 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-86075 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-86075

Explore →

Is Your Infrastructure Affected by CVE-2026-86075?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.