CVE-2026-59257

HIGHNVD 8.88.8
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory published 2026-07-08. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 5 sources updated this week
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

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

n8n before 1.123.61, 2.x before 2.27.4, and 2.28.x before 2.28.1 contains a SQL injection vulnerability in the legacy MySQL v1 node's executeQuery operation. The operation substitutes evaluated {{ ... }} expression values directly into the raw SQL string without parameterization. When a workflow uses this operation with expression-sourced values and is connected to an externally-reachable trigger (such as a Webhook node), attacker-controlled input reaching those expressions results in SQL injection, allowing execution of arbitrary SQL with the configured MySQL credentials' privileges. The MySQL v2 node, which uses parameterized queries, is not affected.

CVSS v3
8.8
EG Score
8.8(high)
EPSS
23.4%
KEV
Not listed

Published

July 8, 2026

Last Modified

July 9, 2026

Advisory Details (2)

Auto-updated Jul 8, 2026
Patch available. Sources: github.
generic

n8n - SQL Injection in MySQL v1 executeQuery Operation via Expression Interpolation | Advisories | VulnCheck

https://www.vulncheck.com/advisories/n8n-sql-injection-in-mysql-v1-executequery-operation-via-expression-interpolation
github Patch Available

MySQL v1 Node executeQuery Operation Allows SQL Injection via Unparameterized Expression Interpolation · Advisory · n8n-io/n8n · GitHub

https://github.com/n8n-io/n8n/security/advisories/GHSA-hwmj-qg4v-cvg9

Vendor Advisories for CVE-2026-59257(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 40× in last 7d / 43× 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-15 18:43 UTCEG score recompute
  2. 2026-07-15 18:43 UTCGHSA enrichment
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 16:57 UTCEPSS rescore
  5. 2026-07-15 06:21 UTCEG score recompute
  6. 2026-07-15 06:21 UTCGHSA enrichment
  7. 2026-07-15 02:00 UTCEPSS rescore
  8. 2026-07-15 02:00 UTCEPSS rescore
  9. 2026-07-14 17:59 UTCEG score recompute
  10. 2026-07-14 17:59 UTCGHSA enrichment
  11. 2026-07-14 05:31 UTCEG score recompute
  12. 2026-07-14 05:31 UTCGHSA enrichment
  13. 2026-07-13 22:31 UTCEPSS rescore
  14. 2026-07-13 17:09 UTCEG score recompute
  15. 2026-07-13 17:09 UTCGHSA enrichment
  16. 2026-07-13 06:13 UTCEPSS rescore
  17. 2026-07-13 06:13 UTCEPSS rescore
  18. 2026-07-13 04:48 UTCEG score recompute
  19. 2026-07-13 04:48 UTCGHSA enrichment
  20. 2026-07-12 16:27 UTCEG score recompute
  21. 2026-07-12 16:27 UTCGHSA enrichment
  22. 2026-07-12 05:46 UTCEPSS rescore
  23. 2026-07-12 04:06 UTCEG score recompute
  24. 2026-07-12 04:06 UTCGHSA enrichment
  25. 2026-07-11 15:42 UTCEG score recompute
Show 18 more
  1. 2026-07-11 15:41 UTCGHSA enrichment
  2. 2026-07-11 08:27 UTCEPSS rescore
  3. 2026-07-11 08:27 UTCEPSS rescore
  4. 2026-07-11 03:20 UTCEG score recompute
  5. 2026-07-11 03:20 UTCGHSA enrichment
  6. 2026-07-10 14:59 UTCEG score recompute
  7. 2026-07-10 14:59 UTCGHSA enrichment
  8. 2026-07-10 02:38 UTCEG score recompute
  9. 2026-07-10 02:37 UTCGHSA enrichment
  10. 2026-07-09 19:10 UTCEPSS rescore
  11. 2026-07-09 19:10 UTCEPSS rescore
  12. 2026-07-09 15:53 UTCNVD updateCVSS v3 → 8.8 · severity → HIGH
  13. 2026-07-09 14:20 UTCMITRE cvelistV5CVSS v3 → 5.3 · severity → MEDIUM
  14. 2026-07-09 14:13 UTCEG score recompute 3.50
  15. 2026-07-09 14:13 UTCGHSA enrichment
  16. 2026-07-08 19:14 UTCNVD updateCVSS v3 → 8.8 · severity → HIGH
  17. 2026-07-08 14:06 UTCEG score recompute
  18. 2026-07-08 14:05 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-59257?
CVE-2026-59257 is a high vulnerability published on July 8, 2026. n8n before 1.123.61, 2.x before 2.27.4, and 2.28.x before 2.28.1 contains a SQL injection vulnerability in the legacy MySQL v1 node's executeQuery operation. The operation substitutes evaluated {{ ... }} expression values directly into the raw SQL string without parameterization. When a workflow…
When was CVE-2026-59257 disclosed?
CVE-2026-59257 was first published in the National Vulnerability Database on July 8, 2026, with the most recent update on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59257 actively exploited?
CVE-2026-59257 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 23.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-59257?
CVE-2026-59257 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-59257?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59257, 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

Explore the affected products and dependency analysis for CVE-2026-59257

Explore →

Is Your Infrastructure Affected by CVE-2026-59257?

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