Skip to main content

MySQL Server CVE-2026-101775

| EUVDEUVD-2026-106176 HIGH
Improper Access Control (CWE-284)
2026-10-20 secalert_us@oracle.com GHSA-76j3-x2q2-g8wr
7.4
CVSS 3.1 · Vendor: oracle
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach MySQL network port remotely
  2. Delivery
    Send crafted replication-protocol traffic
  3. Exploit
    Trigger high-complexity flaw in Server: Replication
  4. Execution
    Corrupt/modify critical data
  5. Impact
    Crash database (complete DoS)

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Access control enforcement
MITRE ATT&CK

1 technique across 1 tactic: Defense Evasion

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation targets the Server: Replication component of MySQL Server (8.4.0-8.4.12, 9.7.0-9.7.3, 26.7.0-26.7.1) and MySQL Cluster (8.0.0-8.0.49, 8.4.0-8.4.12, 9.7.0-9.7.3, 26.7.0-26.7.1), reachable remotely over 'multiple protocols' per Oracle, with no authentication required (PR:N) and no user interaction (UI:N). The decisive LIMITING factor is high attack complexity (AC:H): Oracle explicitly labels it 'difficult to exploit,' implying dependence on specific server state, timing, or race conditions in replication handling rather than a trivially repeatable request. Realistic exposure is confined to database nodes whose network ports are reachable by the attacker; databases bound to localhost or isolated behind strict network segmentation are not reachable. The exact replication configuration or feature needed to trigger the flaw is not specified in the available advisory data and should be verified with Oracle.

Impact

This is a genuine but second-tier priority. The CVSS 3.1 base score of 7.4 is driven by an unauthenticated network vector (AV:N/PR:N/UI:N) combined with high integrity and availability impact (I:H/A:H), but it is materially tempered by high attack complexity (AC:H), which Oracle itself flags in the description as 'difficult to exploit.' There is NO confidentiality impact (C:N) - this is a data-tampering and denial-of-service issue, not a data-theft one. No EPSS score was provided in the input, so exploitation probability cannot be quantified. The CVE is NOT on CISA KEV and no public exploit code is referenced, so there is no evidence of active exploitation or weaponization. The only tags are 'Denial Of Service' and 'Oracle,' consistent with the A:H impact. Net: the raw score looks alarming, but AC:H plus no public exploit, no KEV, and no confidentiality loss means this is a patch-in-normal-cycle issue for most operators rather than an emergency - unless the server is internet-exposed and replication is in use, in which case the DoS and data-integrity risk warrants prioritization. No SSVC decision data was provided in the input and cannot be inferred.

Exploit ScenarioDerived

A remote, unauthenticated attacker with network reachability to a MySQL Server or MySQL Cluster node sends crafted traffic over one of the supported protocols targeting the Replication subsystem, exploiting a difficult-to-trigger flaw to tamper with or destroy replicated data or to force a repeatable crash (complete DoS) of the database. Because attack complexity is high (AC:H), success likely depends on specific timing or server state, and no public proof-of-concept exploit is referenced in the available data.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 21, 2026

Unauthenticated remote attackers can corrupt or destroy data and trigger repeatable crashes of MySQL Server and MySQL Cluster through the Server: Replication component, affecting Server 8.4.0-8.4.12, 9.7.0-9.7.3 and 26.7.0-26.7.1 and 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. Oracle rates it 7.4 (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H), explicitly calling it difficult to exploit, so success likely hinges on specific replication state, timing or race conditions rather than a single crafted request, and there is no confidentiality impact - the exposure is unauthorized creation, deletion or modification of critical data plus a hang or frequently repeatable full denial of service. No public exploit code or confirmed active exploitation was identified at time of analysis, and this is best treated as a genuine but second-tier priority concentrated on database nodes whose ports are network-reachable.

RemediationAI

Apply the fixes published in Oracle's October 2026 Critical Patch Update (https://www.oracle.com/security-alerts/cpuoct2026.html), which is the vendor's patched-version reference for CVE-2026-101775; the supplied data does not state the exact fixed release numbers, so confirm the precise 8.4.x, 9.7.x and 26.7.x patch levels in that advisory before scheduling upgrades, and note that the 8.0.x Cluster line must also be moved to a supported fixed release. Until patching is complete, the highest-value control is reachability reduction, since the vector requires network access: bind MySQL to loopback or a management interface where the workload permits, and restrict 3306, 33060 and the NDB ports (1186 and cluster transport ports) to known application and replica hosts via host firewalls or security groups - the trade-off is that legitimate remote clients and cross-region replication must be explicitly allowlisted or they will break. Isolate replication traffic on a dedicated, encrypted network segment and require TLS with certificate verification for replication accounts, which does not remove the flaw but removes opportunistic internet-wide reachability, at the cost of added certificate management. Because integrity and availability are the impacted metrics, monitor for unexpected server restarts, replication thread aborts, binlog/GTID inconsistencies and replica resynchronization storms as indicators of attempted or successful exploitation. Be aware that Oracle classified this as difficult to exploit, so patching should be prioritized against other exposure factors rather than treated as an emergency stop-the-line action unless the instance is internet-facing.

Affected VersionsENISA

MySQL Cluster 8.0.0-8.0.49
MySQL Cluster 8.4.0-8.4.12
MySQL Cluster 9.7.0-9.7.3
MySQL Server 9.7.0-9.7.3
MySQL Server 8.4.0-8.4.12
MySQL Cluster 26.7.0-26.7.1
MySQL Server 26.7.0-26.7.1

Affected Packages

euvd mysql_cluster no fix
euvd mysql_server no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw sits in MySQL's replication subsystem, the layer that streams binary-log events, GTIDs and (in Cluster/NDB deployments) epoch and redo information between source and replica nodes, and that underpins asynchronous, semi-synchronous and Group Replication topologies. Oracle assigns no CWE for this record, so the precise root-cause class - malformed replication packet/event parsing, state-machine confusion, or a race in replication-thread handling - is not disclosed; the CVSS profile (AC:H, PR:N, UI:N, C:N/I:H/A:H) indicates a remotely reachable defect that requires a narrow, state-dependent condition to reach rather than a straightforwardly repeatable packet. The AC:H metric is the decisive restraint: the attacker must wait for or induce a specific replication configuration, topology state or timing window, which sharply narrows practical exposure compared with typical network-exploitable MySQL bugs. Oracle's phrase "via multiple protocols" covers the classic MySQL client/server protocol (default 3306), the X Protocol (33060) and the NDB Cluster management/transport ports (for example 1186). Because the vector carries PR:N, no credentials are needed, but reachability is the gate: instances bound to localhost, or replication links confined to a segmented, firewalled network, are effectively out of scope for an external attacker. No CPE dictionary entries were supplied with the record; version mapping instead comes from Oracle's affected-range list and the ENISA EUVD entry (EUVD-2026-106176).

Know when MySQL gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (oracle) PRIMARY 7.4 HIGH
AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H
vuln.today AI 7.4 HIGH

Oracle confirms unauthenticated remote access (AV:N/PR:N) but 'difficult to exploit' (AC:H); impact is data integrity and DoS with no data disclosure, so C:N, I:H, A:H.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N
Red Hat 7.4 HIGH

Primary rating from Vendor (oracle).

CVSS VectorVendor: oracle

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

DescriptionCVE.org

Vulnerability in the MySQL Server, MySQL Cluster product of Oracle MySQL (component: Server: Replication). 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. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise MySQL Server, MySQL Cluster. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all MySQL Server, MySQL Cluster accessible data and unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server, MySQL Cluster. CVSS 3.1 Base Score 7.4 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H).

Executive ViewAI

Why It Matters

An unauthenticated, network-reachable defect in the MySQL Server and MySQL Cluster replication component allows an attacker to corrupt or destroy critical data and to trigger repeatable full-service outages, covering Server 8.4.0-8.4.12, 9.7.0-9.7.3 and 26.7.0-26.7.1 and 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. Oracle characterises exploitation as difficult and dependent on specific replication state or timing, and no public exploit or confirmed active exploitation was identified at time of analysis, so leadership exposure is concentrated in integrity and availability of database nodes whose ports are reachable from untrusted networks rather than in data theft.

Business Impact: High
Compensating Controls

No vendor-released patch is identified at time of analysis. Interim mitigations: restrict replication and database ports to an explicit allow-list of trusted peer hosts and block them at the perimeter; segment affected MySQL Server and MySQL Cluster nodes from untrusted networks; remove or disable unnecessary replication endpoints and accounts; monitor for abnormal restarts, crash loops and unexpected data changes as an early indicator; maintain verified, restorable backups and test restoration; and apply the vendor fix as soon as Oracle publishes a release outside the affected version ranges.

Threat Intelligence Overview

EPSS Score
0.4%
Top 73% exploitable
Prevalence
Ubiquitous
MySQL is one of the most widely deployed databases worldwide
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.4%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

37
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +37
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

More in MySQL

View all
CVE-2016-6662 CRITICAL POC
9.8 Sep 20

Oracle MySQL through 5.5.52, 5.6.x through 5.6.33, and 5.7.x through 5.7.15; MariaDB before 5.5.51, 10.0.x before 10.0.2

CVE-2012-5613 MEDIUM POC
6.0 Dec 03

MySQL 5.5.19 and possibly other versions, and MariaDB 5.5.28a and possibly other versions, when configured to assign the

CVE-2017-3599 HIGH POC
7.5 Apr 24

Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: Pluggable Auth). Rated high severity

CVE-2012-2122 MEDIUM POC
5.1 Jun 26

sql/password.c in Oracle MySQL 5.1.x before 5.1.63, 5.5.x before 5.5.24, and 5.6.x before 5.6.6, and MariaDB 5.1.x befor

CVE-2020-5398 HIGH
7.5 Jan 17

In Spring Framework, versions 5.2.x prior to 5.2.3, versions 5.1.x prior to 5.1.13, and versions 5.0.x prior to 5.0.16,

CVE-2012-5612 MEDIUM POC
6.5 Dec 03

Heap-based buffer overflow in Oracle MySQL 5.5.19 and other versions through 5.5.28, and MariaDB 5.5.28a and possibly ot

CVE-2012-5611 MEDIUM POC
6.5 Dec 03

Stack-based buffer overflow in the acl_get function in Oracle MySQL 5.5.19 and other versions through 5.5.28, and 5.1.53

CVE-2020-1967 HIGH POC
7.5 Apr 21

Server or client applications that call the SSL_check_chain() function during or after a TLS 1.3 handshake may crash due

CVE-2016-6664 HIGH POC
7.0 Dec 13

mysqld_safe in Oracle MySQL through 5.5.51, 5.6.x through 5.6.32, and 5.7.x through 5.7.14; MariaDB; Percona Server befo

CVE-2015-3152 MEDIUM POC
5.9 May 16

Oracle MySQL before 5.7.3, Oracle MySQL Connector/C (aka libmysqlclient) before 6.1.3, and MariaDB before 5.5.44 use the

CVE-2026-24479 CRITICAL POC
9.8 Jan 27

HUSTOJ online judge has a path traversal vulnerability enabling arbitrary file access on the competition server.

CVE-2016-2105 HIGH
7.5 May 05

Integer overflow in the EVP_EncodeUpdate function in crypto/evp/encode.c in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2

Vendor StatusVendor

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy