Vulnerability in the MySQL Connectors product of Oracle MySQL (component: Connector/J).

published 2026-10-20 19 d ago modified 2026-10-22 17 d ago also EUVD-2026-106169

cvss: 8.1; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 37%
public exploits: 0; none known

Vulnerability in the MySQL Connectors product of Oracle MySQL (component: Connector/J). The supported version that is affected is 26.7.0. Difficult to exploit vulnerability allows unauthenticated attacker with network access via HTTP to compromise MySQL Connectors. Successful attacks of this vulnerability can result in takeover of MySQL Connectors. CVSS 3.1 Base Score 8.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H).

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-101768 updated 2026-11-04 cvss 8.1

mysql-connector-java: MySQL Connector/J: Unauthenticated remote takeover

Red Hat Enterprise Linux 6 mysql-connector-java 5.1.17-6.el6 Red Hat Enterprise Linux 7 mysql-connector-java 5.1.17-6.el6
not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: total
Assessed: 17 d ago (2026-10-22)

Exploit prediction

0.43% chance of exploitation in the next 30 days, higher than 37% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	8.1	CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Oracle Corporation MySQL Connectors

Classification

Weakness

CWE-284 Improper Access Control

References

oracle.com /security-alerts/cpuoct2026.html
vendor-advisory

Sources

CVE List CVE-2026-101768
NVD CVE-2026-101768

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary