Widely used ProxySQL vulnerability enabling ACL/routing bypass; could disrupt DB access org-wide.
CVE-2026-48772
ProxySQL front-end can forge client_addr via PP1 header, bypassing ACLs.
Is CVE-2026-48772 being exploited?
Not confirmed. CVE-2026-48772 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.21% probability of exploitation in the next 30 days.
How severe is CVE-2026-48772?
CVE-2026-48772 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-48772?
Yes. A fix has been recorded for CVE-2026-48772. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-48772 affect?
CVE-2026-48772 affects ProxySQL 2.0.0–3.0.8 front-end. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-48772?
Upgrade to ProxySQL 3.0.9 or newer
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers can forge client_addr to bypass ACLs and routing, potentially accessing restricted schemas and executing restricted queries.
Patch when possible
- affected>= 2.0.0 and < 3.0.9
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.