CVE-2026-48773
Pre-auth heap corruption in ProxySQL (2.0.18–3.0.8) via oversized first packet.
Is CVE-2026-48773 being exploited?
Not confirmed. CVE-2026-48773 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.47% probability of exploitation in the next 30 days.
How severe is CVE-2026-48773?
CVE-2026-48773 is rated Critical with a CVSS score of 9.8. 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-48773?
Yes. A fix has been recorded for CVE-2026-48773. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-48773 affect?
CVE-2026-48773 affects ProxySQL 2.0.18-3.0.8, ProxySQL MySQL/PostgreSQL protocol handlers. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-48773?
Upgrade to 3.0.9+
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote unauthenticated memory corruption via oversized first packet; may crash ProxySQL or enable remote code execution.
Immediate action required
- affected>= 2.0.18 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.