proxysql vulnerabilities and fixes
Recent CVEs affecting proxysql, with upgrade or downgrade steps. 3 tracked.
proxysql has 3 tracked vulnerabilities, 2 critical. A fixed release or vendor patch exists for 3. Most recent: 2026-06-19. Highest priority: CVE-2026-48773 (score 65/100).
- CVE-2026-48773 CRITICAL 9.8 UPGRADE ProxySQL is a proxy for MySQL and its forks, as well as PostgreSQL
- CVE-2026-48772 CRITICAL 10.0 UPGRADE ProxySQL is a proxy for MySQL and its forks, as well as PostgreSQL
- CVE-2026-48774 HIGH 7.5 UPGRADE ProxySQL is a proxy for MySQL and its forks, as well as PostgreSQL
FAQ
How do I fix proxysql vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is proxysql being exploited right now?
None of the tracked proxysql CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which proxysql CVE should I patch first?
CVE-2026-48773 currently ranks highest (65/100): ProxySQL is a proxy for MySQL and its forks, as well as PostgreSQL.