Skip to main content

MySQL Cluster EUVDEUVD-2026-106170

| CVE-2026-101769 HIGH
Improper Access Control (CWE-284)
2026-10-20 secalert_us@oracle.com GHSA-8g58-crm6-fgqw
7.0
CVSS 3.1 · Vendor: oracle
View

Attack ChainAIDerived

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

  1. Access
    Reach MySQL Cluster node over TCP
  2. Delivery
    Send crafted Cluster protocol traffic
  3. Exploit
    Satisfy high-complexity trigger conditions
  4. Execution
    Crash or hang cluster process
  5. Impact
    Complete DOS plus limited data read/modify

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 requires TCP network access to a MySQL Cluster node running affected versions 26.7.0 or 26.7.1, targeting the Cluster: General component; no authentication and no user interaction are needed (PR:N/UI:N). The key limiting factor is high attack complexity (AC:H) - Oracle explicitly labels this 'difficult to exploit,' meaning the attacker must meet specific conditions or timing beyond the attacker's direct control rather than being able to fire a single reliable request. Practical exposure is further bounded by whether the cluster's data/management network is reachable from untrusted networks; MySQL Cluster is typically deployed on segmented internal networks, which narrows the realistic attacker population.

Impact

This is a genuinely moderate-priority issue rather than a top-tier emergency, and the signals are largely consistent. The CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H) describes a network-reachable, unauthenticated flaw, which raises concern, but the AC:H (high attack complexity - Oracle's own 'difficult to exploit' language) materially lowers real-world likelihood of opportunistic mass exploitation. The dominant impact is availability (A:H = complete DOS via hang or repeatable crash), with only limited confidentiality and integrity impact (C:L/I:L - unauthorized read of a subset and unauthorized update/insert/delete to some data). No EPSS score was supplied, so exploitation probability cannot be quantified from the input. There is no CISA KEV listing and no public exploit identified at time of analysis, so this is not confirmed to be actively exploited. No SSVC decision data was provided. The one point worth verifying: the description states 'Difficult to exploit' yet pairs it with an unauthenticated network vector - the net effect is that while an attacker needs no credentials, they must overcome specific conditions or timing to succeed, which keeps practical risk below the raw 7.0 score. Treat this as a standard patch-cycle priority for MySQL Cluster operators, elevated where the cluster is internet- or untrusted-network-reachable.

Exploit ScenarioDerived

An unauthenticated attacker with TCP network reach to a MySQL Cluster node sends specially crafted traffic to the Cluster: General component to trigger a hang or repeatable crash, producing a complete denial of service, and in some cases achieving limited unauthorized read or modification of cluster-accessible data. Because the CVSS vector marks AC:H, the attacker must satisfy non-trivial conditions or timing, so success is not guaranteed on a single attempt. No public proof-of-concept or exploit code has been identified at time of analysis.

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

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

Alert me

AnalysisAIv1 – Oct 21, 2026

Denial of service and limited data access in MySQL Cluster 26.7.0 and 26.7.1 can be triggered by an unauthenticated attacker with TCP network access to the Cluster: General component. A successful attack can hang or repeatedly crash the cluster (complete availability loss) and expose or modify a subset of cluster-accessible data, with CVSS 3.1 score 7.0. The high attack complexity and the typical deployment of MySQL Cluster on segmented internal networks reduce practical exposure; no public exploit was identified at time of analysis.

RemediationAI

Patch available per vendor advisory: Oracle's October 2026 Critical Patch Update is the remediation reference for MySQL Cluster, though an exact fixed version number was not provided in the input data. Apply the CPU update to MySQL Cluster 26.7.0 and 26.7.1 deployments and verify the installed build against Oracle's advisory. Until patched, restrict TCP access to cluster data, management, and SQL nodes so that only trusted application and administration hosts can reach them; enforce network segmentation and firewall rules for NDB and MySQL ports rather than exposing cluster services to untrusted networks. The trade-off is that overly strict filtering can break legitimate cross-node communication, replication, and client connectivity, so stage and monitor rule changes. Because exploitation requires network access and high-complexity conditions, reducing reachability is the most direct compensating control; no public exploit was identified at time of analysis.

Affected VersionsENISA

MySQL Cluster 26.7.0-26.7.1

Affected Packages

euvd mysql_cluster no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

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

Technical ContextAI · show details

Oracle MySQL Cluster is the NDB-based shared-nothing clustering system for MySQL, with data nodes, management nodes, SQL nodes, and NDB API communication over TCP. The affected component is 'Cluster: General' in MySQL Cluster 26.7.0 through 26.7.1. The CVSS vector AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H indicates network reachability, no authentication or user interaction, a high-complexity attack path, and a primary availability impact with limited confidentiality and integrity impact. The high AC component matches Oracle's 'difficult to exploit' label: the attacker needs conditions or timing beyond a single reliable request. No CWE mapping or CPE strings were provided, so the exact root-cause class cannot be confirmed from the available data; the issue should be treated as a cluster-protocol or service-handling flaw that can disrupt node/cluster availability and touch some cluster-accessible data.

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.0 HIGH
AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H
vuln.today AI 7.0 HIGH

Network TCP vector (AV:N) and no credentials (PR:N), but 'difficult to exploit' justifies AC:H; availability dominates (A:H) with limited C/I (L) per the described data access.

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

Primary rating from Vendor (oracle).

CVSS VectorVendor: oracle

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

DescriptionCVE.org

Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 26.7.0-26.7.1. Difficult to exploit vulnerability allows unauthenticated attacker with network access via TCP to compromise MySQL Cluster. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Cluster as well as unauthorized update, insert or delete access to some of MySQL Cluster accessible data and unauthorized read access to a subset of MySQL Cluster accessible data. CVSS 3.1 Base Score 7.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H).

Executive ViewAI

Why It Matters

MySQL Cluster versions 26.7.0 and 26.7.1 contain a high-severity flaw that can cause complete cluster outages and limited data exposure or modification. No public exploit identified at time of analysis, but the potential availability impact warrants leadership attention. Organizations running these versions should contain network exposure while awaiting a vendor fix.

Business Impact: High
Compensating Controls

Restrict TCP network access to MySQL Cluster General component to trusted segments; enforce network segmentation and least-privilege firewall rules; monitor for abnormal cluster hangs or crashes; maintain tested offline backups and recovery procedures.

Threat Intelligence Overview

EPSS Score
0.3%
Top 81% exploitable
Prevalence
Medium
MySQL Cluster (NDB) is a specialized HA deployment, common but not universal
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.3%
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

35
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +35
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

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