cve.bz

CVE-2026-101768 oracle corporation mysql connectors: Improper Access Control

8.1 highEPSS 0.4%

High (8.1) in oracle corporation mysql connectors. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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).

Severity

CVSS 3.1

8.1 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.4% (unchanged from 0.4% a week ago) estimated probability of exploitation activity in the next 30 days; 38th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-22. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-284 Improper Access Control
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-101768 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-101768?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-101768?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-101768 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • oracle corporation:mysql connectors

Versions

From the CNA's record in the CVE List.

ProductAffected
Oracle Corporation MySQL Connectors26.7.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu14.04:LTSmysql-5.5no fix listedUBUNTU-CVE-2026-101768
Ubuntu20.04:LTSmariadb-10.3no fix listedUBUNTU-CVE-2026-101768
UbuntuPro:16.04:LTS, Pro:18.04:LTSmysql-5.7no fix listedUBUNTU-CVE-2026-101768

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as Important due to the severe potential impact, where a remote attacker could achieve complete compromise of the underlying application environment despite high attack complexity. Red Hat Enterprise Linux packages are not affected by this issue, as the supported releases of mysql-connector-java do not contain the vulnerable upstream code.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 6mysql-connector-javaNot affected
Red Hat Enterprise Linux 7mysql-connector-javaNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-101768.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-284 (17).

References

Check your stackJSON