CVE-2026-48773: ProxySQL pre-auth heap overflow in MySQL and PostgreSQL first-packet handling
ProxySQL is a proxy for MySQL and its forks, as well as PostgreSQL. Versions 2.0.18 through 3.0.8 have a pre-authentication heap memory corruption vulnerability in the MySQL and PostgreSQL protocol first-read paths. A remote unauthenticated client can declare an oversized first packet length, and ProxySQL passes that attacker-controlled length directly to recv() while writing into a fixed 32 KB input queue. Version 3.0.9 patches the issue.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ProxySQLto a version that resolves this vulnerability.Fixed in 3.0.9
Event History
Frequently Asked Questions
What is the severity of CVE-2026-48773?
The severity of CVE-2026-48773 is rated as critical with a score of 9.8.
How do I fix CVE-2026-48773?
To fix CVE-2026-48773, upgrade to ProxySQL version 3.0.9 or later.
What types of databases are affected by CVE-2026-48773?
CVE-2026-48773 affects ProxySQL deployed with MySQL and PostgreSQL databases.
What is the impact of CVE-2026-48773?
CVE-2026-48773 allows a remote unauthenticated client to exploit a heap memory corruption, potentially leading to remote code execution.
Which versions of ProxySQL are vulnerable to CVE-2026-48773?
ProxySQL versions 2.0.18 through 3.0.8 are vulnerable to CVE-2026-48773.