Skip to main content
VulnerabilityPublished

CVE-2026-102664: ProxySQL · Uninitialized heap read in MySQL compressed packet decompression via zlib path

Affects proxysqlSource GCVE Database

0
Compare
Authoritative record:CVE-2026-102664· High 7.1

Not known to be exploited · CVSS 7.1 High · fixed in 4.0.10 : patch proxysql soon.

Data as of 17 Nov 2026, 16:18 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.17.1
Patch
Available – fixed in 4.0.10, 3.1.10, 3.0.10
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade proxysql to 4.0.10, 3.1.10 or 3.0.10.

Affected software

ProductAffectedFixed in
Bitnamiproxysqlpkg:bitnami/proxysqlOther threatsAffected
  • <3.0.10
  • >=3.1.0 <3.1.10
  • >=4.0.0 <4.0.10
Fixed in
  • 3.0.10
  • 3.1.10
  • 4.0.10

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade ProxySQL to version 3.0.10, 3.1.10, or 4.0.10 or later, where this vulnerability is fixed. No other mitigation is indicated or required according to the available data.

Description

ProxySQL versions prior to 3.0.10, 3.1.10, and 4.0.10 contain a vulnerability in the MySQL compressed packet decompression function. An authenticated MySQL client negotiating compression can manipulate the payload length, causing ProxySQL to read uninitialized heap memory and forward stale data to the backend. This can lead to disclosure of prior SQL queries, result data, credentials, or session state, and may also cause excessive memory allocations. The issue is fixed in versions 3.0.10, 3.1.10, and 4.0.10.

References

Community reviews

Loading reviews…