CVE-2026-44791

CRITICALNVD 9.99.9
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.9 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 57% 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
9.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.9Exploit: 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.43, 2.22.1, and 2.20.7, an authenticated user with permission to create or modify workflows could bypass the patch for CVE-2026-42232 in the XML node. When combined with other nodes, this could lead to RCE on the n8n host. This vulnerability is fixed in 1.123.43, 2.22.1, and 2.20.7.

CVSS v3
9.9
EG Score
9.9(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity99% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
43%
KEV
Not listed

Published

June 23, 2026

Last Modified

June 24, 2026

Advisory Details (1)

Auto-updated Aug 23, 2026
Patch available. Sources: github.
github Patch Available

XML Node Prototype Pollution Patch Bypass · Advisory · n8n-io/n8n · GitHub

https://github.com/n8n-io/n8n/security/advisories/GHSA-wrwr-h859-xh2r

Vendor Advisories for CVE-2026-44791(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
n8n2.20.7

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 54× 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-26 14:46 UTCEPSS rescore
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-24 22:05 UTCEG score recompute
  4. 2026-08-24 13:54 UTCEG score recompute
  5. 2026-08-23 02:40 UTCEG score recompute
  6. 2026-08-23 00:19 UTCEPSS rescore
  7. 2026-08-22 01:00 UTCEG score recompute
  8. 2026-08-21 23:49 UTCEPSS rescore
  9. 2026-08-20 23:42 UTCEG score recompute
  10. 2026-08-20 22:55 UTCEPSS rescore
  11. 2026-08-20 07:46 UTCEG score recompute
  12. 2026-08-19 17:04 UTCEPSS rescore
  13. 2026-08-19 04:49 UTCEG score recompute
  14. 2026-08-18 13:48 UTCEPSS rescore
  15. 2026-08-17 14:47 UTCEG score recompute
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-16 15:17 UTCEG score recompute
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 04:13 UTCEG score recompute
  20. 2026-08-16 02:14 UTCEPSS rescore
  21. 2026-08-15 01:30 UTCEG score recompute
  22. 2026-08-15 01:30 UTCEPSS rescore
  23. 2026-08-13 23:41 UTCEG score recompute
  24. 2026-08-13 22:00 UTCEPSS rescore
  25. 2026-08-12 13:51 UTCEG score recompute
Show 72 more
  1. 2026-08-12 13:51 UTCEPSS rescore
  2. 2026-08-11 15:33 UTCEG score recompute
  3. 2026-08-11 00:47 UTCEG score recompute
  4. 2026-08-11 00:00 UTCEPSS rescore
  5. 2026-08-09 14:04 UTCEG score recompute
  6. 2026-08-09 13:46 UTCEPSS rescore
  7. 2026-08-08 19:38 UTCEG score recompute
  8. 2026-08-08 16:37 UTCEPSS rescore
  9. 2026-08-07 17:48 UTCEG score recompute
  10. 2026-08-06 15:57 UTCEG score recompute
  11. 2026-08-06 13:46 UTCEPSS rescore
  12. 2026-08-05 21:08 UTCEG score recompute
  13. 2026-08-05 19:17 UTCEPSS rescore
  14. 2026-08-04 15:14 UTCEG score recompute
  15. 2026-08-04 15:10 UTCEPSS rescore
  16. 2026-08-04 10:38 UTCEPSS rescore
  17. 2026-08-03 14:15 UTCEG score recompute
  18. 2026-08-03 10:36 UTCEPSS rescore
  19. 2026-08-02 02:28 UTCEG score recompute
  20. 2026-08-02 02:27 UTCEPSS rescore
  21. 2026-08-01 04:17 UTCEG score recompute
  22. 2026-08-01 04:16 UTCEPSS rescore
  23. 2026-07-30 17:50 UTCEG score recompute
  24. 2026-07-30 16:28 UTCEPSS rescore
  25. 2026-07-30 02:35 UTCEG score recompute
  26. 2026-07-30 01:30 UTCEPSS rescore
  27. 2026-07-29 01:16 UTCEG score recompute
  28. 2026-07-28 15:36 UTCEPSS rescore
  29. 2026-07-27 17:46 UTCEG score recompute
  30. 2026-07-27 14:13 UTCEPSS rescore
  31. 2026-07-26 15:53 UTCEG score recompute
  32. 2026-07-26 14:54 UTCEPSS rescore
  33. 2026-07-26 14:54 UTCEPSS rescore
  34. 2026-07-25 14:18 UTCEPSS rescore
  35. 2026-07-24 14:17 UTCEPSS rescore
  36. 2026-07-23 14:18 UTCEPSS rescore
  37. 2026-07-23 03:15 UTCEG score recompute
  38. 2026-07-22 14:08 UTCEPSS rescore
  39. 2026-07-21 15:24 UTCEPSS rescore
  40. 2026-07-20 17:08 UTCEPSS rescore
  41. 2026-07-19 14:31 UTCEPSS rescore
  42. 2026-07-19 02:29 UTCEPSS rescore
  43. 2026-07-18 10:04 UTCEPSS rescore
  44. 2026-07-16 17:03 UTCEPSS rescore
  45. 2026-07-15 16:57 UTCEPSS rescore
  46. 2026-07-15 02:00 UTCEPSS rescore
  47. 2026-07-13 22:30 UTCEPSS rescore
  48. 2026-07-13 06:13 UTCEPSS rescore
  49. 2026-07-12 05:46 UTCEPSS rescore
  50. 2026-07-11 08:27 UTCEPSS rescore
  51. 2026-07-09 19:10 UTCEPSS rescore
  52. 2026-07-08 15:16 UTCEPSS rescore
  53. 2026-07-07 13:46 UTCEPSS rescore
  54. 2026-07-06 16:27 UTCEPSS rescore
  55. 2026-07-06 02:23 UTCEPSS rescore
  56. 2026-07-05 02:30 UTCEPSS rescore
  57. 2026-07-04 06:31 UTCEPSS rescore
  58. 2026-07-01 15:07 UTCEPSS rescore
  59. 2026-06-30 23:22 UTCEPSS rescore
  60. 2026-06-29 14:06 UTCEPSS rescore
  61. 2026-06-29 14:06 UTCEPSS rescore
  62. 2026-06-28 14:07 UTCEPSS rescore
  63. 2026-06-28 04:56 UTCEPSS rescore
  64. 2026-06-28 04:56 UTCEPSS rescore
  65. 2026-06-27 03:08 UTCEPSS rescore
  66. 2026-06-25 13:49 UTCEPSS rescore
  67. 2026-06-25 13:49 UTCEPSS rescore
  68. 2026-06-24 19:36 UTCEG score recompute 0.50
  69. 2026-06-24 16:02 UTCNVD updateCVSS v3 → 9.9
  70. 2026-06-24 14:05 UTCEPSS rescore
  71. 2026-06-23 17:35 UTCEG score recompute
  72. 2026-06-23 17:34 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-44791?
CVE-2026-44791 is a critical vulnerability published on June 23, 2026. n8n is an open source workflow automation platform. Prior to 1.123.43, 2.22.1, and 2.20.7, an authenticated user with permission to create or modify workflows could bypass the patch for CVE-2026-42232 in the XML node. When combined with other nodes, this could lead to RCE on the n8n host. This…
When was CVE-2026-44791 disclosed?
CVE-2026-44791 was first published in the National Vulnerability Database on June 23, 2026, with the most recent update on June 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44791 actively exploited?
CVE-2026-44791 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 57.1% of all scored CVEs.
What is the CVSS score of CVE-2026-44791?
CVE-2026-44791 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2026-44791?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44791, 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-44791

Explore →

Is Your Infrastructure Affected by CVE-2026-44791?

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