VulnerabilityPublished 23 Oct 2026Updated 27 Oct 2026

CVE-2026-101678: Mysql 5.5 · (Vulnerability in the MySQL Connectors product of Oracle MySQL (compone ...)

Affects mysql-5.5Source GCVE Database

Authoritative record:CVE-2026-101678· Medium 4.3

Not known to be exploited · CVSS 4.3 Medium.

Data as of 27 Oct 2026, 08:45 UTC

CVSS 3.1 base score

4.3Medium

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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 20.04 LTSmariadb-10.3`pkg:deb/ubuntu/mariadb-10.3?arch=source&distro=focal`Other threats	Affected 1:10.3.17-1 – 1:10.3.39-0ubuntu0.20.04.2 15 affected builds	Fixed in–
Ubuntu Pro 18.04 LTSmysql-5.7`pkg:deb/ubuntu/mysql-5.7?arch=source&distro=esm-infra/bionic`Other threats	Affected 5.7.19-0ubuntu1 – 5.7.44-0ubuntu0.18.04.1+esm1 28 affected builds	Fixed in–
Ubuntu Pro 16.04 LTSmysql-5.7`pkg:deb/ubuntu/mysql-5.7?arch=source&distro=esm-infra/xenial`Other threats	Affected 5.7.11-0ubuntu4 – 5.7.44-0ubuntu0.16.04.1+esm1 36 affected builds	Fixed in–
Ubuntu 14.04 LTSmysql-5.5`pkg:deb/ubuntu/mysql-5.5?arch=source&distro=trusty`Other threats	Affected 5.5.32-0ubuntu7 – 5.5.62-0ubuntu0.14.04.1 25 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

Until a patch is available, consider limiting exposure of affected MySQL connectors to untrusted networks and avoid user interactions that could trigger the vulnerability.

Description

A medium severity vulnerability (CVE-2026-101678) affects specific versions of MySQL 5.5 connectors. The flaw has a CVSS 3.1 base score of 4.3, indicating a network attack vector with low complexity and no privileges required, but requires user interaction and impacts availability only. No confidentiality or integrity impact is reported. The vulnerability is published and affects multiple Ubuntu-packaged MySQL 5.5 versions.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats