CVE-2026-48772

CRITICALPre-NVD 10.010.0
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 10.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (13th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-38074 (ENISA EUVD)Source: ENISA EUVD

10.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 10.0Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

ProxySQL is a proxy for MySQL and its forks, as well as PostgreSQL. In versions 2.0.0 through 3.0.8, the ProxySQL MySQL frontend accepts the PROXY UNKNOWN \r\n PP1 frame as a well-formed PROXY protocol header. The HAProxy PROXY protocol v1 specification says that when the protocol token is UNKNOWN, the receiver MUST ignore any address fields that follow it, because the proxy has declared it cannot determine the client identity. ProxySQL parses those address fields anyway via sscanf and writes the spoofed source address into the session's addr.addr field. From there it flows directly into the query-rule matcher, where the client_addr predicate decides routing and ACL. When mysql-proxy_protocol_networks = '*' (the default), any TCP peer can send a PP1 frame and choose any source IP claim. With that, any mysql_query_rules row pinned to a client_addr value is forgeable: the attacker writes the address they want to match into the PP1 line, and ProxySQL routes their query as if it came from that address. In practice this is a routing and ACL bypass. Real deployments use client_addr for read-write splitting (internal apps go to the primary, public traffic to read replicas), per-app schema pinning, and query-filter rules (DDL allowed only from admin CIDR, public queries blocked from dangerous patterns). An attacker that can reach the frontend port can forge their way into any of those routes. Version 3.0.9 patches this issue.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
76
EG Risk 76/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.
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: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.2%
EPSS %ILE
13th
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.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.2% 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).

A fix is available. 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 Nov 1, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

ProxySQL: PROXY-Protocol-v1 UNKNOWN parses spoofed source IP, bypassing mysql_query_rules.client_addr ACL · Advisory · sysown/proxysql · GitHub

https://github.com/sysown/proxysql/security/advisories/GHSA-gw94-85m2-x8v2
GitHub release Patch Available

ProxySQL 3.0.9

Patch available: sysown/proxysql v3.0.9

https://github.com/sysown/proxysql/releases/tag/v3.0.9

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 57× 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 177 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 77 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-48772?
CVE-2026-48772 is a critical-severity vulnerability; its CVE record was published on June 19, 2026. ProxySQL is a proxy for MySQL and its forks, as well as PostgreSQL. In versions 2.0.0 through 3.0.8, the ProxySQL MySQL frontend accepts the PROXY UNKNOWN <addr> <addr> <port> <port>\r\n PP1 frame as a well-formed PROXY protocol header. The HAProxy PROXY protocol v1 specification says that when the…
When was the CVE record for CVE-2026-48772 published?
The CVE record for CVE-2026-48772 was published on June 19, 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 October 25, 2026; the record at its source may have been updated since.
Is CVE-2026-48772 actively exploited?
CVE-2026-48772 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48772?
CVE-2026-48772 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-48772?
A fix for CVE-2026-48772 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-48772?

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