Sysown vulnerabilities
We track 4 vulnerabilities in Sysown products. 4 are rated high or critical, and none are known to be exploited. The most recent was published on November 4, 2026.
Latest Sysown vulnerabilities
- 7.1 High severity
proxysql: Use of Uninitialized Resource
ProxySQL is a proxy for MySQL and its forks, as well as PostgreSQL. Prior to 3.0.10, 3.1.10, and 4.0.10, decompress_mysql_payload() in lib/mysql_data_stream.cpp accepts a zlib stream when uncompress() returns Z_OK without checking that the actual output length
- 7.5 High severity
ProxySQL is a proxy for MySQL and its forks, as well as PostgreSQL.
ProxySQL is a proxy for MySQL and its forks, as well as PostgreSQL. In versions 3.0.0 through 3.0.8, ProxySQL's GenAI/MCP `run_sql_readonly` tool violates its documented read-only contract for MySQL targets. The tool validates only the full input string with a
- 9.8 Critical severity
proxysql: Out-of-bounds Write
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
- 10.0 Critical severity
proxysql: Use of Less Trusted Source
ProxySQL is a proxy for MySQL and its forks, as well as PostgreSQL. In versions 2.0.0 through 3.0.8, the ProxySQL MySQL frontend accepts the `PROXY UNKNOWN <addr> <addr> <port> <port>\r\n` PP1 frame as a well-formed PROXY protocol header. The HAProxy PROXY pro