CVE-2026-86073

HIGHNVD 7.67.6
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.6 under NVD CVSS v3. EPSS exploit probability: 0.4% (33rd 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
Trending — 3 sources updated this week

Also known asEUVD-2026-73162 (ENISA EUVD) · GHSA-cw9w-vv67-hf73 (GitHub Security Advisories)Source: ENISA EUVD

7.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.6Exploit: 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.1, the OAuth token endpoint bound an authorization code's first access token to the consented resource but did not bind its refresh token. Refreshing checked only that the requested resource was registered, not that it matched the original grant. An OAuth client approved for one workflow could substitute a different workflow URL in the resource parameter and obtain a valid token for an unapproved workflow accessible to the consenting user. This issue is fixed in versions 2.37.7 and 2.38.1.

CVSS v3
7.6
EG Score
7.6HIGHmedium confidence
EG Risk
34
EG Risk 34/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)
Severity76% × 45%
Impact severity (EG Severity): CVSS 7.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.4%
EPSS %ILE
33rd
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.6): severity, escalated by confirmed exploitation. This CVE's 7.6 is its impact severity (EG Severity), not escalated.

EG Severity
7.6 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.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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 every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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 (6)

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

n8n@2.38.1

Patch available: n8n-io/n8n n8n@2.38.1

https://github.com/n8n-io/n8n/releases/tag/n8n@2.38.1
GitHub release Patch Available

n8n@2.37.7

Patch available: n8n-io/n8n n8n@2.37.7

https://github.com/n8n-io/n8n/releases/tag/n8n@2.37.7
GitHub commit

commit 380788fd9a32 (n8n-io/n8n)

Fix landed in n8n-io/n8n commit 380788fd9a32 — awaiting tagged release

https://github.com/n8n-io/n8n/commit/380788fd9a3264c83161e868026a98731d274d88
GitHub pull request

chore: Bundle 2.x (backport to release-candidate/2.37.x)

Fix merged in n8n-io/n8n PR #37588 on 2026-09-02 — awaiting tagged release

https://github.com/n8n-io/n8n/pull/37588
GitHub pull request

fix(core): Bind OAuth token grants to their approved resource

Fix merged in n8n-io/n8n PR #37122 on 2026-08-31 — awaiting tagged release

https://github.com/n8n-io/n8n/pull/37122
GitHub advisoryMentions a patch (unverified)

Per-Resource OAuth Consent Bypass via Unbound Refresh Token Resource Substitution · Advisory · n8n-io/n8n · GitHub

https://github.com/n8n-io/n8n/security/advisories/GHSA-cw9w-vv67-hf73

Vendor Advisories for CVE-2026-86073(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.1 (fixes >= 2.38.0, < 2.38.1)—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.1: fixed in 2.38.1
  • 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 10× in last 7d / 48× 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 it from the CNA feed. 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). Most recent first.

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. 2 repeat rows among the latest 95 are merged into the row they repeat.

  1. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  2. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  3. 2026-11-01 07:38 UTCGHSA enrichmentGHSA-cw9w-vv67-hf73 · GitHub severity MODERATE
  4. 2026-11-01 07:38 UTCEG score recompute
  5. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  6. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  7. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  8. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  9. 2026-10-27 20:05 UTCEG score recompute
  10. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  11. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  12. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  13. 2026-10-25 13:55 UTCEG score recompute
  14. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  15. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  16. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  17. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  19. 2026-10-20 07:29 UTCEG score recompute
  20. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  21. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  22. 2026-10-18 03:05 UTCEG score recompute
  23. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  24. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  25. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
Show 68 more
  1. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  2. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  3. 2026-10-13 05:23 UTCEG score recompute
  4. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  5. 2026-10-12 14:52 UTCEG score recompute
  6. 2026-10-11 19:17 UTCEG score recompute
  7. 2026-10-11 16:30 UTCEG score recompute
  8. 2026-10-11 13:51 UTCEG score recompute
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  11. 2026-10-09 22:29 UTCEG score recompute
  12. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  13. 2026-10-09 00:37 UTCEG score recompute
  14. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  15. 2026-10-08 07:27 UTCEG score recompute
  16. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  17. 2026-10-06 21:34 UTCEG score recompute
  18. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  19. 2026-10-05 22:30 UTCEG score recompute
  20. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  21. 2026-10-05 10:05 UTCEG score recompute
  22. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  23. 2026-10-04 00:45 UTCEG score recompute
  24. 2026-10-03 00:20 UTCEG score recompute
  25. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  26. 2026-10-02 00:28 UTCEG score recompute
  27. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  28. 2026-09-30 15:09 UTCEG score recompute
  29. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  30. 2026-09-30 02:19 UTCEG score recompute
  31. 2026-09-28 23:32 UTCEG score recompute
  32. 2026-09-27 14:13 UTCEG score recompute
  33. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  34. 2026-09-27 02:33 UTCEG score recompute
  35. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  36. 2026-09-26 04:20 UTCEG score recompute
  37. 2026-09-24 18:58 UTCEG score recompute
  38. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  39. 2026-09-23 20:45 UTCEG score recompute
  40. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  41. 2026-09-22 22:33 UTCEG score recompute
  42. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  43. 2026-09-22 00:20 UTCEG score recompute
  44. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  45. 2026-09-21 02:07 UTCEG score recompute
  46. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  47. 2026-09-19 16:48 UTCEG score recompute
  48. 2026-09-19 05:41 UTCEG score recompute
  49. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  50. 2026-09-17 20:19 UTCEG score recompute
  51. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  52. 2026-09-16 21:17 UTCEG score recompute
  53. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  54. 2026-09-16 09:23 UTCEG score recompute
  55. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  56. 2026-09-15 11:09 UTCEG score recompute
  57. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  58. 2026-09-14 01:50 UTCEG score recompute
  59. 2026-09-12 16:26 UTCEG score recompute
  60. 2026-09-11 18:13 UTCEG score recompute▲ 1.70
  61. 2026-09-11 18:13 UTCNVD updateCVSS v3 → 7.6 · severity → HIGH
  62. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  63. 2026-09-10 21:15 UTCEG score recompute
  64. 2026-09-09 16:52 UTCEG score recompute
  65. 2026-09-09 16:03 UTCEG score recompute
  66. 2026-09-08 18:13 UTCEG score recompute
  67. 2026-09-08 17:06 UTCEG score recomputeFirst assessed: 5.9 MEDIUM
  68. 2026-09-08 17:04 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-86073?
CVE-2026-86073 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.1, the OAuth token endpoint bound an authorization code's first access token to the consented resource but did not bind its refresh token. Refreshing checked only that the requested resource was registered, not that it…
When was the CVE record for CVE-2026-86073 published?
The CVE record for CVE-2026-86073 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-86073 actively exploited?
CVE-2026-86073 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-86073?
CVE-2026-86073 has a CVSS v3 base score of 7.6 (NVD).
How do I remediate CVE-2026-86073?
A fix for CVE-2026-86073 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-86073 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-86073

Explore →

Is Your Infrastructure Affected by CVE-2026-86073?

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

Book a Demo →Browse All CVEs