CVE-2026-59971

CRITICALPre-NVD 10.010.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-11. A secondary CVSS source baseline 10.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-78580 (ENISA EUVD) · GHSA-rqfv-2mw9-78g2 (GitHub Security Advisories)Source: ENISA EUVD

10.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 10.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

MySQL MCP Server is a Model Context Protocol server that enables secure interaction with MySQL databases. Prior to 0.4.2, setting MCP_TRANSPORT=sse causes src/mysql_mcp_server/server.py to construct SseServerTransport without security_settings or enable_dns_rebinding_protection, while the Starlette routes /, /sse, and /messages/ have no authentication and the service binds to 0.0.0.0 by default. A network attacker can directly reach execute_sql, or can use DNS rebinding to make a victim's browser relay same-origin requests to a locally bound service, and supply a query that reaches cursor.execute(query). This allows unauthenticated disclosure and modification of the configured database; when the MySQL account has FILE privileges, the same access can read or write server files and may enable code execution. The default stdio transport is not affected. This issue is fixed in 0.4.2.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
45
EG Risk 45/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
36th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 11, 2026

Last Modified

September 30, 2026

Advisory Details (4)

Auto-updated Oct 30, 2026
Patch available. Sources: github, github_commit, github_release.
GitHub advisoryMentions a patch (unverified)

Missing Origin/Host Validation in SSE Transport Enables Unauthenticated SQL Execution (DNS Rebinding / Direct Exposure) · Advisory · designcomputer/mysql_mcp_server · GitHub

https://github.com/designcomputer/mysql_mcp_server/security/advisories/GHSA-rqfv-2mw9-78g2
GitHub release Patch Available

v0.4.2

Patch available: designcomputer/mysql_mcp_server v0.4.2

https://github.com/designcomputer/mysql_mcp_server/releases/tag/v0.4.2
Web page

Missing Origin/Host Validation in SSE Transport Enables Unauthenticated `execute_sql` (DNS Rebinding / Direct Exposure → Full Database Compromise) · Issue #92 · designcomputer/mysql_mcp_server · GitHub

https://github.com/designcomputer/mysql_mcp_server/issues/92
GitHub commit Patch Available

commit a96549f4a4d6 (designcomputer/mysql_mcp_server)

Patch available: designcomputer/mysql_mcp_server v0.4.2 (contains commit a96549f4a4d6)

https://github.com/designcomputer/mysql_mcp_server/commit/a96549f4a4d65443fd6e9c7f2324fba9a5c80a82

Vendor Advisories for CVE-2026-59971(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipmysql-mcp-server @ 0.4.2 (fixes < 0.4.2)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
mysql-mcp-server0.1.0 ... 0.4.1 (9 versions)
  • every version up to 0.4.2: fixed in 0.4.2
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 68× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 102 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 2 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 23:44 UTCEG score recompute
  2. 2026-11-01 23:44 UTCGHSA enrichmentGHSA-rqfv-2mw9-78g2 · GitHub severity CRITICAL · GitHub CVSS 10.0
  3. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  4. 2026-11-01 07:41 UTCGHSA enrichmentGHSA-rqfv-2mw9-78g2 · GitHub severity CRITICAL · GitHub CVSS 10.0
  5. 2026-11-01 07:41 UTCEG score recompute
  6. 2026-10-31 23:40 UTCEG score recompute
  7. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  8. 2026-10-30 23:36 UTCEG score recompute
  9. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  10. 2026-10-29 23:31 UTCEG score recompute
  11. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  12. 2026-10-28 23:27 UTCEG score recompute
  13. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  14. 2026-10-27 23:20 UTCEG score recompute
  15. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  16. 2026-10-26 23:14 UTCEG score recompute
  17. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  18. 2026-10-25 19:44 UTCEG score recompute
  19. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  20. 2026-10-25 14:16 UTCEG score recompute
  21. 2026-10-24 19:40 UTCEG score recompute
  22. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  23. 2026-10-23 19:36 UTCEG score recompute
  24. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  25. 2026-10-22 19:25 UTCEG score recompute
Show 75 more
  1. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  2. 2026-10-21 19:20 UTCEG score recompute
  3. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  4. 2026-10-20 19:16 UTCEG score recompute
  5. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  6. 2026-10-19 19:11 UTCEG score recompute
  7. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  8. 2026-10-18 19:05 UTCEG score recompute
  9. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  10. 2026-10-18 03:26 UTCEG score recompute
  11. 2026-10-17 18:57 UTCEG score recompute
  12. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  13. 2026-10-16 18:53 UTCEG score recompute
  14. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  15. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  16. 2026-10-15 16:04 UTCEG score recompute
  17. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  18. 2026-10-14 10:13 UTCEG score recompute
  19. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  20. 2026-10-13 08:36 UTCEG score recompute
  21. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  22. 2026-10-12 15:52 UTCEG score recompute
  23. 2026-10-11 19:36 UTCEG score recompute
  24. 2026-10-11 16:51 UTCEG score recompute
  25. 2026-10-11 14:13 UTCEG score recompute
  26. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  27. 2026-10-11 11:39 UTCEG score recompute
  28. 2026-10-10 20:20 UTCEG score recompute
  29. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  30. 2026-10-09 20:23 UTCEG score recompute
  31. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  32. 2026-10-08 23:10 UTCEG score recompute
  33. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  34. 2026-10-08 03:15 UTCEG score recompute
  35. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  36. 2026-10-06 16:23 UTCEG score recompute
  37. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  38. 2026-10-05 20:20 UTCEG score recompute
  39. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  40. 2026-10-05 03:15 UTCEG score recompute
  41. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  42. 2026-10-03 14:48 UTCEG score recompute
  43. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  44. 2026-10-02 18:40 UTCEG score recompute
  45. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  46. 2026-10-01 22:27 UTCEG score recompute
  47. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  48. 2026-09-30 17:41 UTCEG score recompute
  49. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  50. 2026-09-30 01:39 UTCEG score recompute
  51. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  52. 2026-09-28 22:35 UTCEG score recompute
  53. 2026-09-28 14:40 UTCEG score recompute
  54. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  55. 2026-09-27 14:47 UTCEG score recompute
  56. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  57. 2026-09-26 18:43 UTCEG score recompute
  58. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  59. 2026-09-26 01:11 UTCEG score recompute
  60. 2026-09-24 15:13 UTCEG score recompute
  61. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  62. 2026-09-23 19:25 UTCEG score recompute
  63. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  64. 2026-09-22 15:30 UTCEG score recompute
  65. 2026-09-21 23:37 UTCEG score recompute
  66. 2026-09-20 23:51 UTCEG score recompute
  67. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  68. 2026-09-19 16:02 UTCEG score recompute
  69. 2026-09-18 20:12 UTCEG score recompute
  70. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  71. 2026-09-17 19:37 UTCEG score recompute
  72. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  73. 2026-09-16 17:59 UTCEG score recompute
  74. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  75. 2026-09-15 16:34 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-59971?
CVE-2026-59971 is a critical-severity vulnerability; its CVE record was published on September 11, 2026. MySQL MCP Server is a Model Context Protocol server that enables secure interaction with MySQL databases. Prior to 0.4.2, setting MCP_TRANSPORT=sse causes src/mysql_mcp_server/server.py to construct SseServerTransport without security_settings or enable_dns_rebinding_protection, while the Starlette…
When was the CVE record for CVE-2026-59971 published?
The CVE record for CVE-2026-59971 was published on September 11, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-59971 actively exploited?
CVE-2026-59971 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-59971?
CVE-2026-59971 has a CVSS base score of 10.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-59971?
A fix for CVE-2026-59971 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-59971 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-59971

Explore →

Is Your Infrastructure Affected by CVE-2026-59971?

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