cve.bz

CVE-2026-101756 oracle: Improper Access Control

4.9 mediumEPSS 0.4%

Medium (4.9) in oracle. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
Vulnerability in the MySQL Server, MySQL Cluster product of Oracle MySQL (component: Server: GIS). Supported versions that are affected are MySQL Server: 9.7.0-9.7.3, 26.7.0-26.7.1; MySQL Cluster: 9.7.0-9.7.3 and 26.7.0-26.7.1. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server, MySQL Cluster. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server, MySQL Cluster. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).

Severity

CVSS 3.1

4.9 medium
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
EPSS
0.4% (unchanged from 0.4% a week ago) estimated probability of exploitation activity in the next 30 days; 39th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, 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
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-101756 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-101756?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-101756?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-101756 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.

Badge for a README or a site

CVE-2026-101756

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-101756](https://cve.bz/cve/badge/CVE-2026-101756.svg)](https://cve.bz/cve/CVE-2026-101756)

HTML:

<a href="https://cve.bz/cve/CVE-2026-101756"><img src="https://cve.bz/cve/badge/CVE-2026-101756.svg" alt="CVE-2026-101756"></a>

Affected

Versions

From the NVD's CPE matches.

ProductAffected
oracle:mysql_clusterfrom 9.7.0 through 9.7.3
oracle:mysql_clusterfrom 26.7.0 through 26.7.1
oracle:mysql_serverfrom 9.7.0 through 9.7.3
oracle:mysql_serverfrom 26.7.0 through 26.7.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu14.04:LTSmysql-5.5no fix listedUBUNTU-CVE-2026-101756
Ubuntu16.04:LTSmariadb-10.0, percona-server-5.6, percona-xtradb-cluster-5.6no fix listedUBUNTU-CVE-2026-101756
Ubuntu18.04:LTSmariadb-10.1no fix listedUBUNTU-CVE-2026-101756
Ubuntu20.04:LTSmariadb-10.3no fix listedUBUNTU-CVE-2026-101756
Ubuntu22.04:LTSmariadb-10.6no fix listedUBUNTU-CVE-2026-101756
Ubuntu22.04:LTSmysql-8.08.0.46-0ubuntu0.22.04.5USN-9046-1
Ubuntu24.04:LTSmysql-8.08.0.46-0ubuntu0.24.04.5USN-9046-1
Ubuntu24.04:LTS, 26.04:LTS, 26.10mariadbno fix listedUBUNTU-CVE-2026-101756
Ubuntu26.04:LTSmysql-8.48.4.13-0ubuntu0.26.04.2USN-9046-1
Ubuntu26.10mysql-9.79.7.4-0ubuntu0.26.10.1UBUNTU-CVE-2026-101756 USN-9046-1
UbuntuPro:16.04:LTS, Pro:18.04:LTSmysql-5.7no fix listedUBUNTU-CVE-2026-101756

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 Moderate.

Red Hat's statement

This vulnerability is rated as Moderate because exploitation requires high administrative privileges, preventing unauthenticated attackers or standard users from triggering the issue. Although an attacker with elevated credentials can induce a hang or crash of the database daemon, the impact is confined to availability without compromising confidentiality or integrity. Furthermore, supported database packages in Red Hat Enterprise Linux do not include the vulnerable code and are not affected.

Red Hat's mitigation

Restrict network exposure of the MySQL daemon to authorized management endpoints using firewall rules:

```

firewall-cmd --permanent --zone=public --remove-service=mysql

firewall-cmd --permanent --zone=trusted --add-source=<TRUSTED_IP_OR_SUBNET>

firewall-cmd --reload

```

Additionally, enforce the principle of least privilege by restricting administrative database roles and permissions to verified personnel only.

Caveats: Limiting network reachability blocks all inbound client connections that do not originate from the specified trusted address ranges.

Warning: Reloading firewall settings may terminate existing connections or disrupt active database sessions.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10mysql8.4Not affected
Red Hat Enterprise Linux 6mysqlNot affected
Red Hat Enterprise Linux 9mysqlNot affected
Red Hat Hardened Imagesmariadb10.11Not affected
Red Hat Hardened Imagesmariadb11.8Not 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-101756.

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