CVE-2026-54312

HIGHNVD 8.58.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 79% 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.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.5Exploit: NoneExposed: 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.24.0, an authenticated user with permission to create or modify workflows could achieve global prototype pollution via the Microsoft SQL node by supplying a crafted value as the table parameter. This pollutes Object.prototype process-wide for the lifetime of the n8n server process, causing application-wide validation failures and rendering the n8n instance completely non-functional until restarted. This vulnerability is fixed in 2.24.0.

CVSS v3
8.5
EG Score
8.5(medium)
EPSS
21.2%
KEV
Not listed

Published

June 16, 2026

Last Modified

June 25, 2026

Advisory Details (1)

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

Microsoft SQL Node Prototype Pollution · Advisory · n8n-io/n8n · GitHub

https://github.com/n8n-io/n8n/security/advisories/GHSA-x6p3-m6h9-fx7r

Vendor Advisories for CVE-2026-54312(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.24.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 23× in last 7d / 60× 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-07-06 22:57 UTCEG score recompute
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-05 22:09 UTCEG score recompute
  7. 2026-07-05 10:54 UTCEG score recompute
  8. 2026-07-05 02:31 UTCEPSS rescore
  9. 2026-07-05 02:30 UTCEPSS rescore
  10. 2026-07-04 23:38 UTCEG score recompute
  11. 2026-07-04 12:24 UTCEG score recompute
  12. 2026-07-04 06:31 UTCEPSS rescore
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-04 00:58 UTCEG score recompute
  15. 2026-07-03 13:44 UTCEG score recompute
  16. 2026-07-03 01:10 UTCEG score recompute
  17. 2026-07-02 13:55 UTCEG score recompute
  18. 2026-07-02 02:41 UTCEG score recompute
  19. 2026-07-01 15:27 UTCEG score recompute
  20. 2026-07-01 15:07 UTCEPSS rescore
  21. 2026-07-01 04:12 UTCEG score recompute
  22. 2026-06-30 23:22 UTCEPSS rescore
  23. 2026-06-30 16:58 UTCEG score recompute
  24. 2026-06-30 05:43 UTCEG score recompute
  25. 2026-06-29 18:29 UTCEG score recompute
Show 35 more
  1. 2026-06-29 07:15 UTCEG score recompute
  2. 2026-06-28 20:00 UTCEG score recompute
  3. 2026-06-28 14:07 UTCEPSS rescore
  4. 2026-06-28 08:46 UTCEG score recompute
  5. 2026-06-28 04:56 UTCEPSS rescore
  6. 2026-06-28 04:56 UTCEPSS rescore
  7. 2026-06-27 21:32 UTCEG score recompute
  8. 2026-06-27 10:18 UTCEG score recompute
  9. 2026-06-27 03:08 UTCEPSS rescore
  10. 2026-06-26 23:03 UTCEG score recompute
  11. 2026-06-26 11:49 UTCEG score recompute
  12. 2026-06-25 22:41 UTCEG score recompute▲ 1.30
  13. 2026-06-25 19:49 UTCNVD updateCVSS v3 → 8.5
  14. 2026-06-25 13:49 UTCEPSS rescore
  15. 2026-06-25 11:27 UTCEG score recompute
  16. 2026-06-25 00:12 UTCEG score recompute
  17. 2026-06-24 14:05 UTCEPSS rescore
  18. 2026-06-24 12:57 UTCEG score recompute
  19. 2026-06-24 00:44 UTCEG score recompute▼ 1.30
  20. 2026-06-23 15:45 UTCMITRE cvelistV5CVSS v3 → 7.2 · CVSS v4 → 7.2
  21. 2026-06-23 13:29 UTCEG score recompute
  22. 2026-06-23 02:13 UTCEG score recompute
  23. 2026-06-22 14:58 UTCEG score recompute
  24. 2026-06-22 03:33 UTCEG score recompute
  25. 2026-06-21 16:16 UTCEG score recompute
  26. 2026-06-21 04:34 UTCEG score recompute
  27. 2026-06-20 17:07 UTCEG score recompute
  28. 2026-06-20 05:52 UTCEG score recompute
  29. 2026-06-19 18:26 UTCEG score recompute
  30. 2026-06-19 07:10 UTCEG score recompute
  31. 2026-06-18 19:46 UTCEG score recompute
  32. 2026-06-18 08:32 UTCEG score recompute
  33. 2026-06-17 21:12 UTCEG score recompute
  34. 2026-06-17 09:58 UTCEG score recompute
  35. 2026-06-16 22:44 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54312?
CVE-2026-54312 is a high vulnerability published on June 16, 2026. n8n is an open source workflow automation platform. Prior to 2.24.0, an authenticated user with permission to create or modify workflows could achieve global prototype pollution via the Microsoft SQL node by supplying a crafted value as the table parameter. This pollutes Object.prototype…
When was CVE-2026-54312 disclosed?
CVE-2026-54312 was first published in the National Vulnerability Database on June 16, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54312 actively exploited?
CVE-2026-54312 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 21.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54312?
CVE-2026-54312 has a CVSS v3 base score of 8.5 (NVD).
How do I remediate CVE-2026-54312?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54312, 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-54312

Explore →

Is Your Infrastructure Affected by CVE-2026-54312?

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

Start Free Scan →Browse All CVEs