CVE-2026-86073

HIGHNVD 7.67.6—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.6 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 87% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.6Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.6(medium)
EG Risk
34(Track)
EG Risk 34/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity76% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
13%
KEV
Not listed

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

[email protected]

Patch available: n8n-io/n8n [email protected]

https://github.com/n8n-io/n8n/releases/tag/[email protected]
github_release Patch Available

[email protected]

Patch available: n8n-io/n8n [email protected]

https://github.com/n8n-io/n8n/releases/tag/[email protected]
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_pr

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_pr

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 Patch Available

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.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
n8n—2.38.1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-09-19 05:41 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 20:19 UTCEG score recompute
  4. 2026-09-17 19:32 UTCEPSS rescore
  5. 2026-09-16 21:17 UTCEG score recompute
  6. 2026-09-16 14:09 UTCEPSS rescore
  7. 2026-09-16 09:23 UTCEG score recompute
  8. 2026-09-16 05:15 UTCEPSS rescore
  9. 2026-09-15 11:09 UTCEG score recompute
  10. 2026-09-15 03:12 UTCEPSS rescore
  11. 2026-09-15 03:12 UTCEPSS rescore
  12. 2026-09-14 01:50 UTCEG score recompute
  13. 2026-09-12 16:26 UTCEG score recompute
  14. 2026-09-11 18:13 UTCEG score recompute▲ 1.70
  15. 2026-09-11 18:13 UTCNVD updateCVSS v3 → 7.6 · severity → HIGH
  16. 2026-09-11 14:53 UTCEPSS rescore
  17. 2026-09-11 14:53 UTCEPSS rescore
  18. 2026-09-10 21:15 UTCEG score recompute
  19. 2026-09-09 16:52 UTCEG score recompute
  20. 2026-09-09 16:03 UTCEG score recompute
  21. 2026-09-08 18:13 UTCEG score recompute
  22. 2026-09-08 17:06 UTCEG score recompute
  23. 2026-09-08 17:04 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-86073?
CVE-2026-86073 is a high vulnerability 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 CVE-2026-86073 disclosed?
CVE-2026-86073 was first published in the National Vulnerability Database on September 8, 2026, with the most recent update on September 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-86073 actively exploited?
CVE-2026-86073 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 87.5% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-86073, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs