VulnerabilityPublished 4 Nov 2026

CVE-2026-102664: sysown proxysql · Use of Uninitialized Resource

Affects sysown proxysqlSource CVE Database V5

Compare

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

Data as of 4 Nov 2026, 23:44 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.1	7.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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 4 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade sysown proxysql to 4.0.10, 3.1.10 or 3.0.10.

Affected software

Product	Affected	Fixed in
sysownproxysql	Affected >=4.0.0 <4.0.10	Fixed in 4.0.10
sysownproxysql	Affected >=3.1.0 <3.1.10	Fixed in 3.1.10
sysownproxysql	Affected <3.0.10	Fixed in 3.0.10

AI-suggested

This vulnerability is fixed in ProxySQL versions 3.0.10, 3.1.10, and 4.0.10. Users should upgrade to one of these versions or later to remediate the issue. No other mitigation or workaround is indicated by the vendor advisory.

Description

CVE-2026-102664 is a vulnerability in ProxySQL prior to versions 3.0.10, 3.1.10, and 4.0.10. It involves improper handling of compressed MySQL payloads where the decompression function does not verify that the output length matches the attacker-controlled payload length. This can lead to the proxy forwarding uninitialized heap buffer data to the backend, potentially disclosing sensitive information such as prior SQL queries, result data, credentials, or session state. The flaw also allows malformed lengths to cause excessive memory allocations. The issue has been fixed in the specified versions.

Impact

An authenticated MySQL client exploiting this vulnerability can cause ProxySQL to forward uninitialized heap memory contents to the backend, potentially disclosing sensitive information including prior SQL queries, result data, credentials, or session state. The vulnerability also allows malformed payload lengths to trigger excessive memory allocations, which could impact availability. The CVSS score of 7.1 reflects a high severity with network attack vector, low attack complexity, and no user interaction required. The confidentiality impact is high, integrity impact is none, and availability impact is low.

CWE-908Use of Uninitialized Resource (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
The product uses or accesses a resource that has not been initialized.
Implementation
Explicitly initialize the resource before use. If this is performed through an API function or standard procedure, follow all required steps.
Implementation
Pay close attention to complex conditionals that affect initialization, since some branches might not perform the initialization.
Implementation
Avoid race conditions (CWE-362) during initialization routines.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2026, 21:01 UTC

WeaknessesCWE-908

Technical details

References

Community reviews

Related threats