Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with low-privileged MySQL account
-
ExploitAbuse privilege-handling flaw over network
-
ImpactRead or modify all accessible data
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 attacker to already possess a valid low-privileged account on the target MySQL Server or MySQL Cluster (PR:L) and network reachability over one of the supported MySQL protocols (AV:N). The vulnerability lies in the Server's Security: Privileges component. The key limiting factor is AC:H (high attack complexity): Oracle explicitly describes it as 'difficult to exploit,' meaning success depends on conditions or state the attacker cannot fully control, not a default one-shot request. No user interaction is required (UI:N). Affected and therefore vulnerable deployments are 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; instances where untrusted or low-trust users hold database accounts are most exposed, while databases reachable only by fully trusted administrators face lower realistic risk. |
| Impact | This is a moderate-priority issue, not a top-tier emergency. The CVSS 3.1 base score of 6.8 (MEDIUM) reflects a genuinely constrained attack: AV:N gives network reach via multiple protocols, but AC:H (high complexity) means exploitation requires specialized conditions, timing, or state that an attacker cannot reliably control, and PR:L requires the attacker to already hold a valid low-privileged MySQL account. The impact is serious where it succeeds - C:H and I:H allow reading, creating, deleting, or modifying all database-accessible data - but A:N means no availability/denial-of-service dimension. No EPSS score, no CISA KEV listing, and no POC were provided in the input, so there is NO evidence of active exploitation or public exploit code; exploitation status is 'no public exploit identified at time of analysis.' The combination of AC:H plus PR:L substantially lowers real-world likelihood relative to the full-access impact, so this should be scheduled as routine Oracle CPU patching rather than emergency remediation. Note a metadata conflict: the input Tags list 'Authentication Bypass,' but the CVSS vector specifies PR:L (an authenticated, low-privileged attacker), which contradicts a true authentication bypass - this is a post-authentication privilege/authorization flaw, verify against the Oracle advisory. |
| Exploit ScenarioDerived | An attacker who already holds a low-privileged MySQL account (for example, a limited application or reporting user) connects over the network via one of the supported protocols and exploits a flaw in the Server's privilege-handling logic to read, create, modify, or delete data they should not be able to reach, up to all database-accessible data. Because the CVSS vector is AC:H, the attack requires specific conditions or state that are not trivially reproducible. No public exploit code was identified in the provided intelligence. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Low-privileged MySQL Server and MySQL Cluster users with network access can potentially gain read and write access to data beyond their intended authorization scope through the Server: Security: Privileges component. The issue affects 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, and Oracle characterizes exploitation as difficult with CVSS 6.8, AC:H, and PR:L. This is a moderate-priority issue, not a top-tier emergency; no public exploit identified at time of analysis, and no CISA KEV entry was present in the supplied intelligence.
RemediationAI
Patch available per vendor advisory: apply the Oracle MySQL fixes published in the October 2026 Critical Patch Update at https://www.oracle.com/security-alerts/cpuoct2026.html; the supplied data does not provide exact fixed version numbers, so use the fixed release Oracle identifies for the applicable MySQL Server 8.4, 9.7, or 26.7 line and MySQL Cluster 8.0, 8.4, 9.7, or 26.7 line rather than inferring a version. Until patched, restrict network reachability to MySQL protocols from trusted application hosts, remove or disable low-trust database accounts, and review grants for privilege-escalation paths; these controls may disrupt legitimate application connectivity or break workflows that depend on the removed accounts. Monitor for unexpected privilege changes and abnormal data access, because no public exploit identified at time of analysis does not remove the need for least-privilege enforcement.
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 flaw sits in MySQL Server's Server: Security: Privileges component, which governs account privileges and authorization decisions, and Oracle's affected matrix spans both standalone MySQL Server and MySQL Cluster. The assessed vector CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N indicates network reachability over supported MySQL protocols, a high-complexity attack path, a valid low-privileged account, no user interaction, unchanged scope, and high confidentiality and integrity impact with no availability impact. The supplied tag labels this Authentication Bypass, but the assessed prerequisites still require a valid low-privileged account, so the practical concern is an authorization or privilege-boundary failure rather than unauthenticated entry. No CWE was provided, and no CPE strings were included in the source 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
AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
Network-reachable over MySQL protocols (AV:N) but Oracle-described as difficult (AC:H) and requires an existing low-privileged account (PR:L); full read/write data impact (C:H/I:H) with no availability effect (A:N).
Primary rating from Vendor (oracle).
CVSS VectorVendor: oracle
DescriptionCVE.org
Vulnerability in the MySQL Server, MySQL Cluster product of Oracle MySQL (component: Server: Security: Privileges). 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 low privileged 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 as well as unauthorized access to critical data or complete access to all MySQL Server, MySQL Cluster accessible data. CVSS 3.1 Base Score 6.8 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N).
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-106201
GHSA-hcq4-f5vq-2fpp
NVD
CVE.org
EPSS
Exploit-DB