ProxySQL is a proxy for MySQL and its forks, as well as PostgreSQL. In versions 3.0.0 through 3.0.8, ProxySQL's GenAI/MCP run_sql_readonly tool violates its documented read-only contract for MySQL targets. The tool validates only the full input string with a substring blacklist and first-keyword allowlist, but then executes the entire SQL string on a backend connection created with CLIENT_MULTI_STATEMENTS. As a result, a caller can submit a read-only first statement followed by a side-effecting second statement, such as SELECT 1; RENAME TABLE .... The validator accepts the payload because it starts with SELECT and because side-effecting MySQL statements such as RENAME TABLE, SET, RESET, LOCK TABLES, and KILL are not rejected by the blacklist. In a live MCP runtime test, the /mcp/query endpoint accepted a run_sql_readonly request. The MCP response reported success for the first SELECT, and direct backend verification showed that the table had actually been renamed. This violates the endpoint's read-only security contract and lets an MCP caller perform backend writes or administrative SQL, limited by the configured MCP target account's database privileges. Version 3.0.9 contains a fix. Other operator mitigations include: keeping MCP disabled unless required; setting a non-empty mcp-query_endpoint_auth token before exposing /mcp/query; restricting MCP listener network exposure; configuring MCP backend target credentials as database-level read-only users; and adding temporary MCP query rules to block obvious multi-statement patterns.
CVE-2026-48774
“—” beside the score: it is equal to the CVSS score beside it.
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (33rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2026-38075 (ENISA EUVD)Source: ENISA EUVD
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
The CVE record names the fixed release — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5HIGHmedium confidence
- EG Risk
- 65EG Risk 65/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)Severity75% × 45%Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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: The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.4%
- EPSS %ILE
- 33rd
- 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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- 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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).
The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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; 60 days if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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
June 19, 2026
Last Modified
October 25, 2026
Advisory Details (2)
Auto-updated Jun 19, 2026ProxySQL MCP run_sql_readonly executes side-effecting MySQL multi-statements despite read-only contract · Advisory · sysown/proxysql · GitHub
https://github.com/sysown/proxysql/security/advisories/GHSA-7wh6-2vcc-gcm4commit e32b7fd50c7c (sysown/proxysql)
Fix landed in sysown/proxysql commit e32b7fd50c7c — awaiting tagged release
https://github.com/sysown/proxysql/commit/e32b7fd50c7c234ea628e392e621e09a2a919e08Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 39× 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 163 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 63 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-02 14:19 UTCEG score recompute
- 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-25 23:34 UTCEG score recompute
- 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-25 14:23 UTCEG score recompute
- 2026-10-25 03:03 UTCEG score recompute
- 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-18 03:34 UTCEG score recompute
- 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-17 12:16 UTCEG score recompute
- 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
Show 75 moreShow fewer
- 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-12 16:00 UTCEG score recompute
- 2026-10-11 19:43 UTCEG score recompute
- 2026-10-11 16:58 UTCEG score recompute
- 2026-10-11 14:22 UTCEG score recompute
- 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-03 05:09 UTCOSV refresh
- 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-09-14 02:20 UTCEG score recompute
- 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-09-13 13:08 UTCEG score recompute
- 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-08-30 20:47 UTCEG score recompute
- 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-08-24 22:17 UTCEG score recompute
- 2026-08-23 12:51 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-08-22 23:40 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-08-21 10:27 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-08-20 08:00 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-08-19 07:00 UTCEG score recompute
- 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-08-17 16:05 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-08-17 02:53 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-08-16 13:41 UTCEG score recompute
- 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-08-15 11:19 UTCEG score recompute
- 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-08-14 08:51 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-08-12 17:16 UTCEG score recompute
- 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-08-11 14:53 UTCEG score recompute
- 2026-08-11 01:41 UTCEG score recompute
- 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-08-09 18:22 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-08-09 05:10 UTCEG score recompute
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-48774?
When was the CVE record for CVE-2026-48774 published?
Is CVE-2026-48774 actively exploited?
What is the CVSS score of CVE-2026-48774?
How do I remediate CVE-2026-48774?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-48774
Is Your Infrastructure Affected by CVE-2026-48774?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.