cve.bz

CVE-2026-101781 oracle: Improper Access Control

8.8 highEPSS 0.4%

High (8.8) 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: Group Replication GCS). Supported versions that are affected are MySQL Server: 8.4.0-8.4.12, 9.7.0-9.7.3, 26.7.0-26.7.1; MySQL Cluster: 8.0.0-8.0.49, 8.4.0-8.4.12, 9.7.0-9.7.3 and 26.7.0-26.7.1. Easily exploitable vulnerability allows unauthenticated attacker with access to the physical communication segment attached to the hardware where the MySQL Server, MySQL Cluster executes to compromise MySQL Server, MySQL Cluster. Successful attacks of this vulnerability can result in takeover of MySQL Server, MySQL Cluster. CVSS 3.1 Base Score 8.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:A/AC:L/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; 34th 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: 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
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

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

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-101781](https://cve.bz/cve/badge/CVE-2026-101781.svg)](https://cve.bz/cve/CVE-2026-101781)

HTML:

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

Affected

Versions

From the NVD's CPE matches.

ProductAffected
oracle:mysql_clusterfrom 8.0.0 through 8.0.49
oracle:mysql_clusterfrom 8.4.0 through 8.4.12
oracle:mysql_clusterfrom 9.7.0 through 9.7.3
oracle:mysql_clusterfrom 26.7.0 through 26.7.1
oracle:mysql_serverfrom 8.4.0 through 8.4.12
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-101781
Ubuntu16.04:LTSmariadb-10.0, percona-server-5.6, percona-xtradb-cluster-5.6no fix listedUBUNTU-CVE-2026-101781
Ubuntu18.04:LTSmariadb-10.1no fix listedUBUNTU-CVE-2026-101781
Ubuntu20.04:LTSmariadb-10.3no fix listedUBUNTU-CVE-2026-101781
Ubuntu22.04:LTSmariadb-10.6no fix listedUBUNTU-CVE-2026-101781
Ubuntu22.04:LTSmysql-8.08.0.46-0ubuntu0.22.04.5UBUNTU-CVE-2026-101781 USN-9046-1
Ubuntu24.04:LTSmysql-8.08.0.46-0ubuntu0.24.04.5UBUNTU-CVE-2026-101781 USN-9046-1
Ubuntu24.04:LTS, 26.04:LTS, 26.10mariadbno fix listedUBUNTU-CVE-2026-101781
Ubuntu26.04:LTSmysql-8.48.4.13-0ubuntu0.26.04.2UBUNTU-CVE-2026-101781 USN-9046-1
Ubuntu26.10mysql-9.79.7.4-0ubuntu0.26.10.1UBUNTU-CVE-2026-101781 USN-9046-1
UbuntuPro:16.04:LTS, Pro:18.04:LTSmysql-5.7no fix listedUBUNTU-CVE-2026-101781
UbuntuPro:20.04:LTSmysql-8.0no fix listedUBUNTU-CVE-2026-101781
Red Hatenterprise_linux:9::appstreammecab, mecab-devel, mecab-debuginfo and 1 more0:0.996-3.module+el9.9.0+24089+64aac046.4RHSA-2026:99741
Red Hatenterprise_linux:9::appstreammecab-ipadic, mecab-ipadic-EUCJP0:2.7.0.20070801-24.module+el9.9.0+24089+64aac046RHSA-2026:99741
Red Hatenterprise_linux:9::appstreammysql, mysql-libs, mysql-test and 11 more0:8.4.13-1.module+el9.9.0+25300+c0fc77bcRHSA-2026:99741
Red Hatenterprise_linux:9::appstreamperl-DBD-MySQL, perl-DBD-MySQL-debuginfo, perl-DBD-MySQL-debugsource0:4.053-3.module+el9.9.0+24089+64aac046RHSA-2026:99741
Red Hatenterprise_linux:9::appstreamrapidjson, rapidjson-doc, rapidjson-devel0:1.1.0-20.module+el9.9.0+25300+c0fc77bcRHSA-2026:99741
Red Hatenterprise_linux:10.3mysql8.4, mysql8.4-libs, mysql8.4-test and 11 more0:8.4.13-1.el10_3RHSA-2026:99720
Rocky Linux9mecab0:0.996-3.module+el9.8.0+40162+a76274f1.4RLSA-2026:99741
Rocky Linux9mecab0:0.996-3.module+el9.8.0+40205+77f4da59.4RLSA-2026:99741
Rocky Linux9mecab-ipadic0:2.7.0.20070801-24.module+el9.8.0+40162+a76274f1RLSA-2026:99741
Rocky Linux9mecab-ipadic0:2.7.0.20070801-24.module+el9.8.0+40205+77f4da59RLSA-2026:99741
Rocky Linux9perl-DBD-MySQL0:4.053-3.module+el9.8.0+40162+a76274f1RLSA-2026:99741
Rocky Linux9perl-DBD-MySQL0:4.053-3.module+el9.8.0+40205+77f4da59RLSA-2026:99741

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; Rocky Linux's errata, BSD-3-Clause. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu · Red Hat.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as Important because an unauthenticated adjacent attacker can achieve complete system compromise without requiring prior privileges or user interaction. Standard MySQL installations on Red Hat Enterprise Linux do not enable Group Replication by default, leaving typical standalone deployments unaffected. Risk is confined to environments where Group Replication is actively configured and group communication ports are accessible from untrusted adjacent networks.

Red Hat's mitigation

Restrict network exposure by limiting communication on the Group Replication port to authorized cluster nodes using firewalld, or disable the Group Replication feature if it is not required.

1. Restrict the replication communication port (default TCP 33061) to trusted cluster peer IPs using firewalld:

# firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="<PEER_NODE_IP>" port port="33061" protocol="tcp" accept'

# firewall-cmd --reload

2. Alternatively, if Group Replication is not required, stop the plugin within MySQL:

mysql> STOP GROUP_REPLICATION;

Ensure that `plugin-load` or `group_replication` startup parameters are removed or disabled in the MySQL configuration files under `/etc/my.cnf` or `/etc/my.cnf.d/`.

Caveats: Limiting network access requires specifying all legitimate member addresses; misconfiguration may prevent nodes from joining the replication cluster.

Warning: Reloading firewall rules or stopping the replication service will temporarily interrupt replication traffic and cluster synchronization.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10mysql8.4Affected
Red Hat Enterprise Linux 6mysqlOut of support scope
Red Hat Enterprise Linux 8mysql:8.4/mysqlAffected
Red Hat Enterprise Linux 9mysql:8.4/mysqlAffected
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-101781.

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