CVE-2026-86076

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 63% 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
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: 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 1.123.76, 2.37.7, and 2.38.2, the expression compiler sanitizer resolved through dynamically scoped this and did not reject reserved class member names. A class field named __sanitize could rebind the sanitizer and reach the Function constructor, enabling backend code execution and editor-preview JavaScript execution. The affected AST hook is PrototypeSanitizer in packages/workflow/src/expression-sandboxing.ts. This issue is fixed in versions 1.123.76, 2.37.7 and 2.38.2.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

September 8, 2026

Last Modified

September 11, 2026

Advisory Details (4)

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

Expression Sandbox Escape via Class-Field Sanitizer Rebinding Can Lead to Code Execution · Advisory · n8n-io/n8n · GitHub

https://github.com/n8n-io/n8n/security/advisories/GHSA-hw8v-xxg5-vvvx

Vendor Advisories for CVE-2026-86076(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
n8n1.123.76

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 21× 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-18 22:23 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 20:16 UTCEG score recompute
  4. 2026-09-17 19:32 UTCEPSS rescore
  5. 2026-09-16 16:05 UTCEG score recompute
  6. 2026-09-16 14:09 UTCEPSS rescore
  7. 2026-09-16 05:15 UTCEPSS rescore
  8. 2026-09-15 13:58 UTCEG score recompute
  9. 2026-09-15 03:12 UTCEPSS rescore
  10. 2026-09-15 03:12 UTCEPSS rescore
  11. 2026-09-13 22:49 UTCEG score recompute
  12. 2026-09-12 20:43 UTCEG score recompute
  13. 2026-09-11 18:35 UTCEG score recompute 0.10
  14. 2026-09-11 18:34 UTCNVD updateCVSS v3 → 8.8
  15. 2026-09-11 11:58 UTCEG score recompute
  16. 2026-09-10 09:52 UTCEG score recompute
  17. 2026-09-09 16:46 UTCEG score recompute
  18. 2026-09-09 16:02 UTCEG score recompute
  19. 2026-09-08 22:28 UTCEG score recompute
  20. 2026-09-08 21:41 UTCEG score recompute
  21. 2026-09-08 21:39 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-86076?
CVE-2026-86076 is a high vulnerability published on September 8, 2026. n8n is an open source workflow automation platform. Prior to 1.123.76, 2.37.7, and 2.38.2, the expression compiler sanitizer resolved through dynamically scoped this and did not reject reserved class member names. A class field named sanitize could rebind the sanitizer and reach the Function…
When was CVE-2026-86076 disclosed?
CVE-2026-86076 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-86076 actively exploited?
CVE-2026-86076 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 63.3% of all scored CVEs.
What is the CVSS score of CVE-2026-86076?
CVE-2026-86076 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-86076?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-86076, 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-86076

Explore →

Is Your Infrastructure Affected by CVE-2026-86076?

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