CVE-2026-72749

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 76% 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, secondary
Trending — 3 sources updated this week
7.1EG
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.1Exploit: None knownExposed: 0

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

n8n before 1.123.67, 2.31.5, and 2.32.1 contains a prototype pollution vulnerability in the Edit Fields (Set) node. The node assigns output fields via a dot-notation path setter without restricting the field name, allowing an authenticated user to name a field after an inherited built-in method path and corrupt a shared global in the main Node.js process. Because that global is used on the request-authentication path, the instance then fails every authenticated request, causing an instance-wide denial of service for all users until the process is restarted.

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

Published

August 11, 2026

Last Modified

August 11, 2026

Advisory Details (2)

Auto-updated Aug 11, 2026
Patch available. Sources: github.
generic

n8n before 1.123.67 Prototype Pollution via Edit Fields | Advisories | VulnCheck

https://www.vulncheck.com/advisories/n8n-before-prototype-pollution-via-edit-fields
github Patch Available

Prototype Pollution via Dot-Notation Field Names Leads To Instance-Wide Denial of Service · Advisory · n8n-io/n8n · GitHub

https://github.com/n8n-io/n8n/security/advisories/GHSA-xwx6-jjhv-84p8

Vendor Advisories for CVE-2026-72749(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—1.123.67—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 31× in last 7d / 47× 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-08-21 04:18 UTCEG score recompute
  2. 2026-08-21 04:18 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 17:06 UTCGHSA enrichment
  5. 2026-08-20 05:54 UTCGHSA enrichment
  6. 2026-08-19 18:41 UTCEG score recompute
  7. 2026-08-19 18:41 UTCGHSA enrichment
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-19 06:01 UTCGHSA enrichment
  10. 2026-08-18 18:44 UTCEG score recompute
  11. 2026-08-18 18:44 UTCGHSA enrichment
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 13:49 UTCEPSS rescore
  14. 2026-08-18 07:32 UTCGHSA enrichment
  15. 2026-08-17 20:19 UTCEG score recompute
  16. 2026-08-17 20:19 UTCGHSA enrichment
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-17 09:06 UTCGHSA enrichment
  19. 2026-08-16 21:54 UTCEG score recompute
  20. 2026-08-16 21:54 UTCGHSA enrichment
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 10:41 UTCEG score recompute
  24. 2026-08-16 10:41 UTCGHSA enrichment
  25. 2026-08-16 02:15 UTCEPSS rescore
Show 22 more
  1. 2026-08-15 23:30 UTCGHSA enrichment
  2. 2026-08-15 12:18 UTCEG score recompute
  3. 2026-08-15 12:18 UTCGHSA enrichment
  4. 2026-08-15 01:31 UTCEPSS rescore
  5. 2026-08-15 01:05 UTCGHSA enrichment
  6. 2026-08-14 13:53 UTCGHSA enrichment
  7. 2026-08-14 02:41 UTCEG score recompute
  8. 2026-08-14 02:41 UTCGHSA enrichment
  9. 2026-08-13 22:00 UTCEPSS rescore
  10. 2026-08-13 15:29 UTCGHSA enrichment
  11. 2026-08-13 04:16 UTCGHSA enrichment
  12. 2026-08-12 17:04 UTCEG score recompute
  13. 2026-08-12 17:04 UTCGHSA enrichment
  14. 2026-08-12 13:51 UTCEPSS rescore
  15. 2026-08-12 05:52 UTCGHSA enrichment
  16. 2026-08-11 18:39 UTCEG score recompute
  17. 2026-08-11 18:39 UTCGHSA enrichment
  18. 2026-08-11 18:13 UTCEG score recompute
  19. 2026-08-11 18:13 UTCGHSA enrichment
  20. 2026-08-11 13:25 UTCEG score recompute
  21. 2026-08-11 12:22 UTCEG score recompute
  22. 2026-08-11 12:22 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72749?
CVE-2026-72749 is a high vulnerability published on August 11, 2026. n8n before 1.123.67, 2.31.5, and 2.32.1 contains a prototype pollution vulnerability in the Edit Fields (Set) node. The node assigns output fields via a dot-notation path setter without restricting the field name, allowing an authenticated user to name a field after an inherited built-in method…
When was CVE-2026-72749 disclosed?
CVE-2026-72749 was first published in the National Vulnerability Database on August 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-72749 actively exploited?
CVE-2026-72749 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 76.4% of all scored CVEs.
What is the CVSS score of CVE-2026-72749?
CVE-2026-72749 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-72749?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72749, 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-72749

Explore →

Is Your Infrastructure Affected by CVE-2026-72749?

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

Start Free Scan →Browse All CVEs