CVE-2026-101779VulnerabilityPublished 26 Oct 2026Updated 27 Oct 2026

Mysql 5.5: CVE-2026-101779 affects MySQL Server, MySQL Cluster (Server: Telemetry)

Affects mysql-5.5Source GCVE Database

Authoritative record:CVE-2026-101779· Low 2.7

Not known to be exploited · CVSS 2.7 Low.

Data as of 27 Oct 2026, 08:30 UTC

CVSS 3.1 base score

2.7Low

How severe the flaw is on the 0–10 CVSS scale.

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: None
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: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
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: None: There is no loss of confidentiality within the impacted component.
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 20 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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

Affected software

Product	Affected	Fixed in
Ubuntu 26.10mariadb`pkg:deb/ubuntu/mariadb?arch=source&distro=stonking`Other threats	Affected =1:11.8.6-5 =1:11.8.8-1 =1:11.8.9+ds-4ubuntu2	Fixed in–
Ubuntu 26.10mysql-9.7`pkg:deb/ubuntu/mysql-9.7?arch=source&distro=stonking`Other threats	Affected =9.7.2-4 =9.7.2-4ubuntu1	Fixed in–
Ubuntu 26.04 LTSmariadb`pkg:deb/ubuntu/mariadb?arch=source&distro=resolute`Other threats	Affected 1:11.8.3-1build1 – 1:11.8.6-5ubuntu0.1 10 affected builds	Fixed in–
Ubuntu 26.04 LTSmysql-8.4`pkg:deb/ubuntu/mysql-8.4?arch=source&distro=resolute`Other threats	Affected 8.4.6-0ubuntu3 – 8.4.11-0ubuntu0.26.04.1 7 affected builds	Fixed in–
Ubuntu 24.04 LTSmariadb`pkg:deb/ubuntu/mariadb?arch=source&distro=noble`Other threats	Affected 1:10.11.4-1 – 1:10.11.14-0ubuntu0.24.04.1 10 affected builds	Fixed in–
Ubuntu 24.04 LTSmysql-8.0`pkg:deb/ubuntu/mysql-8.0?arch=source&distro=noble`Other threats	Affected 8.0.34-1ubuntu1 – 8.0.46-0ubuntu0.24.04.4 22 affected builds	Fixed in–

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

AI-suggested

Oracle has released patches for this vulnerability as part of the October 2026 Critical Patch Update. Users should apply the official Oracle patches promptly to mitigate this vulnerability. Oracle strongly recommends running actively supported versions and applying security patches without delay to prevent exploitation. Since this is not a cloud service, patching must be performed by the customer. No alternative mitigations or workarounds are specified in the advisory.

Description

CVE-2026-101779 is a security vulnerability affecting MySQL Server and MySQL Cluster, specifically impacting telemetry components. It affects certain versions of MySQL including 8.4 and 9.7 series. The vulnerability was published on October 26, 2026, and is classified with medium severity. Oracle has released a Critical Patch Update in October 2026 that addresses this and many other vulnerabilities across multiple Oracle products. Customers are strongly advised to apply the available patches promptly to mitigate the risk.

Impact

The vulnerability impacts MySQL Server and MySQL Cluster telemetry components, potentially allowing attackers to exploit the flaw if the system is unpatched. The medium severity rating indicates a moderate risk level. Oracle's advisory notes that exploitation attempts have occurred for vulnerabilities with existing patches, underscoring the importance of timely patching. No confirmed active exploitation or public exploit code is currently known.

Summary

CVE-2026-101779 affects MySQL Server and MySQL Cluster telemetry components in versions 8.4 and 9.7. This vulnerability is included in Oracle's October 2026 Critical Patch Update, which contains 1295 security patches for various Oracle products. The advisory emphasizes the importance of applying patches without delay, as Oracle has observed attempts to exploit vulnerabilities for which patches already exist. The affected product versions include multiple Ubuntu-specific builds of MySQL 5.5, but the advisory primarily references fixes in later MySQL versions (8.4.0-8.4.12, 9.7.0-9.7.3). No public exploit code or active exploitation in the wild has been reported.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Oct 2026, 08:30 UTC

Technical details

References

Community reviews

Related threats