Quick answers
- Is CVE-2026-102664 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-102664 being exploited in the wild.
- How severe is CVE-2026-102664?
- High severity, with a CVSS score of 7.1, published 4 November 2026.
- Which products and versions are affected?
- ProxySQL before 3.0.10, 3.1.10, and 4.0.10.
- Is there a fix for CVE-2026-102664?
- Yes: fixed in 3.0.10, 3.1.10, 4.0.10. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-102664 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-102664?
- Check whether you run ProxySQL at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 3.0.10, 3.1.10, 4.0.10
Technical details
The decompress_mysql_payload() function in lib/mysql_data_stream.cpp fails to validate that zlib decompression actually wrote the number of bytes claimed in the packet header; an attacker can declare a larger payload_length while sending a compressed stream that inflates to fewer bytes, leaving the heap buffer tail uninitialized. The vulnerable code then parses this stale memory as MySQL packet headers and forwards it to the backend, enabling information disclosure. An authenticated MySQL client that negotiates compression is required; no network-level authentication bypass is needed.
Affected products
- ProxySQL ProxySQL before 3.0.10, 3.1.10, and 4.0.10
Timeline
- 2026-11-04: disclosed