Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain foothold on adjacent replication segment
-
DeliverySend crafted GCS Group Replication traffic
-
ExploitExploit Group Replication GCS flaw
-
ExecutionAchieve code execution / instance takeover
-
ImpactFull compromise of MySQL Server/Cluster
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 the target MySQL Server or MySQL Cluster to be running Group Replication (the vulnerable 'Server: Group Replication GCS' / Group Communication System component), which is used in high-availability clustered deployments and is not part of a standalone default install - this is the primary limiting factor. The attacker must also have access to the physical communication segment attached to the hardware where MySQL executes (AV:A, adjacent network / same L2 segment or replication VLAN), so remote internet-based exploitation is not possible. No authentication is required (PR:N), no user interaction is needed (UI:N), and attack complexity is low (AC:L), so any unauthenticated actor already on that replication segment can attempt it against affected versions (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, 26.7.0-26.7.1). |
| Impact | CVSS 3.1 base score is 8.8 (High) with vector AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, indicating an adjacent-network, low-complexity, unauthenticated attack requiring no user interaction and yielding full confidentiality, integrity and availability loss ('takeover'). The decisive and often-overlooked signal here is AV:A (Adjacent), not AV:N: the attacker must sit on the same physical communication segment/L2 broadcast domain as the MySQL host, which materially narrows the attack surface compared to a true internet-facing flaw. No EPSS score, CISA KEV listing, SSVC decision data, or public POC is present in the provided intelligence, so exploitation is currently 'no public exploit identified at time of analysis'; there is no evidence of active exploitation. This should be treated as a genuine high-severity patch priority for clustered MySQL deployments that run Group Replication, but it is NOT an internet-wide spray threat - the adjacent-network constraint and the requirement that the Group Replication/GCS feature be in use place it below a hypothetical AV:N RCE of the same score. The 'Information Disclosure' input tag conflicts with the description, which states full takeover with C:H/I:H/A:H - the impact is far broader than information disclosure alone, so defenders should not down-scope remediation based on that tag. |
| Exploit ScenarioDerived | An attacker positioned on the same network segment as a MySQL cluster node sends crafted Group Communication System (GCS) traffic to the Group Replication transport, exploiting the flaw without any credentials or user interaction to gain full control of the MySQL Server/Cluster instance. No public exploit code has been identified at the time of analysis. Because the CVSS vector is AV:A, the attacker must already have a foothold on the adjacent/replication network rather than attacking across the internet. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Full takeover of MySQL Server and MySQL Cluster is possible for unauthenticated attackers who can reach the Group Replication communication segment, affecting MySQL Server 8.4.0-8.4.12, 9.7.0-9.7.3 and 26.7.0-26.7.1 plus 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. The flaw is in the Server: Group Replication GCS component and yields high confidentiality, integrity and availability impact (CVSS 8.8, AV:A/AC:L/PR:N/UI:N). Exploitation is limited to deployments running Group Replication and to attackers on the adjacent physical communication segment; no public exploit was identified at time of analysis and CISA KEV status is not indicated.
RemediationAI
Apply the Oracle MySQL fix referenced in Oracle's October 2026 Critical Patch Update at https://www.oracle.com/security-alerts/cpuoct2026.html; the provided data does not specify an exact fixed version, so confirm the patched release in the vendor advisory before upgrading. If immediate patching is not possible, disable Group Replication on MySQL Server or MySQL Cluster instances that do not require high-availability clustering, accepting the side effect of losing group replication and failover capabilities. Isolate replication traffic to a dedicated VLAN or network segment with strict ACLs that permit only trusted MySQL nodes, recognizing that this reduces but does not eliminate risk from an attacker already on the same Layer 2 segment. Restrict physical access to the communication segment attached to the MySQL hardware and monitor for anomalous Group Replication traffic. No public exploit was identified at time of analysis, and no CISA KEV active-exploitation status is indicated.
Affected VersionsENISA
Affected Packages
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 affected technology is MySQL's Group Replication Group Communication System (GCS), the group communication layer used by MySQL Server and MySQL Cluster to coordinate membership and message exchange among replication group members in high-availability clustered deployments. The issue is not present in a standalone default MySQL install unless Group Replication is running. The CVSS 3.1 vector AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H describes an adjacent-network attack that is low complexity, requires no authentication and no user interaction, and results in high confidentiality, integrity and availability impact; the independent assessment confirms the primary limiting factors are that Group Replication must be enabled and the attacker must have access to the physical communication segment attached to the MySQL hardware. No CWE identifier was provided in the input, so the root-cause class cannot be mapped from the supplied data. No CPE strings were supplied.
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
AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Description confirms adjacent-segment (AV:A), unauthenticated (PR:N), no-interaction, low-complexity attack yielding full takeover, so C:H/I:H/A:H with unchanged scope.
Primary rating from Vendor (oracle).
CVSS VectorVendor: oracle
DescriptionCVE.org
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).
Executive ViewAI
MySQL Server and MySQL Cluster deployments that use Group Replication face a high-severity takeover risk from unauthenticated attackers who can reach the replication communication segment. The affected product ranges are MySQL Server 8.4.0-8.4.12, 9.7.0-9.7.3, and 26.7.0-26.7.1, plus 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. Leadership should prioritize affected database estates because successful exploitation could compromise data confidentiality, integrity, and availability, although risk is concentrated in Group Replication environments with adjacent network exposure; no public exploit identified at time of analysis and no vendor-released patch identified at time of analysis.
No vendor-released patch identified at time of analysis; interim mitigations include restricting access to the Group Replication communication segment through firewall/ACL segmentation and trusted-host allowlists, disabling Group Replication where not operationally required, monitoring replication-segment traffic for anomalous access, and applying vendor workarounds when published.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
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
MySQL 5.5.19 and possibly other versions, and MariaDB 5.5.28a and possibly other versions, when configured to assign the
Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: Pluggable Auth). Rated high severity
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
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,
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
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
Server or client applications that call the SSL_check_chain() function during or after a TLS 1.3 handshake may crash due
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
Oracle MySQL before 5.7.3, Oracle MySQL Connector/C (aka libmysqlclient) before 6.1.3, and MariaDB before 5.5.44 use the
HUSTOJ online judge has a path traversal vulnerability enabling arbitrary file access on the competition server.
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
EUVD-2026-106182
GHSA-q6xq-6vm7-7h7j
NVD
CVE.org
EPSS
Exploit-DB