ProxySQL pre-auth heap overflow in MySQL and PostgreSQL first-packet handling
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Code execution
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-787 and the CVSS impact.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- Yes
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
- Fix · CNA proxysql (sysown) Fixed in 3.0.9
Vendor assessments
Timeline
- 2026-10-02 Threatist record created from CVE-2026-48773
References
More sysown Proxysql vulnerabilities
- TI-2026-36042 ProxySQL: PROXY-Protocol-v1 UNKNOWN parses spoofed source IP, bypassing mysql_query_rules.client_addr ACL CVSS 3.1CRITICAL 10.0
- TI-2026-36044 ProxySQL MCP run_sql_readonly executes side-effecting MySQL multi-statements despite read-only contract CVSS 3.1HIGH 7.5
Sources
- CVE-2026-48773 · CVE Program
- CVE-2026-48773 · NVD
- FIRST EPSS
- CVE-2026-48773 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences