Security Advisory - Published 2026-06-20 - ProxySQL
ProxySQL 3.0.9 security batch: patch frontends and review MCP exposure
CVE-2026-48772, CVE-2026-48773, and CVE-2026-48774 affect ProxySQL deployments that expose MySQL/PostgreSQL proxy services or the newer GenAI/MCP surface. Treat internet-facing ProxySQL listeners as urgent. Patch first, then review crashes, restarts, connection spikes, and any database writes through tools expected to be read-only.
Affected ProxySQL items
| CVE | Affected | Review | CVSS |
|---|---|---|---|
| CVE-2026-48772 | 2.0.0 through 3.0.8 | ProxySQL listeners, crashes, restarts, and frontend access | 10.0 |
| CVE-2026-48773 | 2.0.18 through 3.0.8 | ProxySQL process crashes, listener exposure, and connection spikes | 9.8 |
| CVE-2026-48774 | 3.0.0 through 3.0.8 | MCP/GenAI settings, tool logs, and database write activity | 7.5 |
Owner self-check
proxysql --version
systemctl status proxysql --no-pager
ss -lntp | egrep '6032|6033|proxysql'
journalctl -u proxysql --since '7 days ago' --no-pager | egrep -i 'crash|segfault|restart|mcp|genai|error'
grep -Rni 'mysql_ifaces\\|pgsql_ifaces\\|admin-mysql_ifaces\\|mcp\\|genai' /etc/proxysql* /var/lib/proxysql* 2>/dev/nullWhat to review
- Any ProxySQL frontend listener reachable from the public internet or broad office networks.
- Unexpected service restarts, segmentation faults, memory corruption messages, or connection spikes.
- GenAI/MCP settings, tool logs, and database writes that should not come from read-only workflows.
- Database accounts used by ProxySQL, including whether they have write privileges that are not needed.
Safe fix path
- Upgrade ProxySQL to 3.0.9 or newer.
- Bind administrative and proxy listeners to trusted interfaces only.
- Disable GenAI/MCP surfaces until tool permissions, logs, and network exposure are reviewed.
- Rotate database credentials if suspicious write activity, service instability, or unknown clients are found.
Repair help
Use Ping7 CVE Repair when ProxySQL was exposed, databases show unexpected writes, or proxy logs are too noisy to separate normal client traffic from suspicious activity.