What is the CVSS score of CVE-2026-47023?

CVE-2026-47023 has a CVSS 3.1 base score of 4.9 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H. EPSS exploitation probability: 0.3%.

Is there a patch available for CVE-2026-47023?

Yes, a patch is available for CVE-2026-47023. Update the affected software to the latest version immediately.

MySQL Server CVE-2026-47023

EUVD-2026-46511 MEDIUM

Uncontrolled Resource Consumption (CWE-400)

2026-07-21 oracle

GHSA-7hrr-qm54-fxvq

Denial Of Service Oracle Red Hat Mysql Cluster Mysql Server Suse Oracle Corporation

4.9

CVSS 3.1 · Vendor: oracle

Severity by source

Vendor (oracle) PRIMARY

4.9 MEDIUM

AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H

vuln.today AI

4.9 MEDIUM

Network-accessible replication component requires high database privileges; impact is exclusively availability within the unscoped affected instance, with no confidentiality or integrity effect.

3.1 AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H

4.0 AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

SUSE

MEDIUM

qualitative

Red Hat

4.9 MEDIUM

qualitative

Primary rating from Vendor (oracle).

CVSS VectorVendor: oracle

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Lifecycle Timeline

Analysis Generated

Jul 22, 2026 - 02:42 vuln.today

CVE Published

Jul 21, 2026 - 21:33 nvd

MEDIUM 4.9

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.10, 9.7.0-9.7.1; MySQL Cluster: 8.0.0-8.0.47, 8.4.0-8.4.10 and 9.7.0-9.7.1. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server, MySQL Cluster. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server, MySQL Cluster. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).

AnalysisAI

Denial of service in Oracle MySQL Server and MySQL Cluster's Replication component allows a high-privileged, network-connected attacker to cause repeated crashes or indefinite hangs across affected 8.0, 8.4, and 9.7 release branches. Exploitation is straightforward (AC:L) but gated entirely by the requirement for high database privileges, substantially narrowing the realistic threat population. No public exploit identified at time of analysis and no CISA KEV listing; risk is most acute in replication-dependent high-availability clusters where availability SLAs are critical.

Technical ContextAI

The vulnerability resides in the Replication subsystem of Oracle MySQL Server and MySQL Cluster - the component responsible for synchronizing data changes across instances in primary/replica and cluster topologies. Affected products are identified by CPE strings cpe:2.3:a:oracle_corporation:mysql_server:*:*:*:*:*:*:*:* and cpe:2.3:a:oracle_corporation:mysql_cluster:*:*:*:*:*:*:*:* across the 8.0, 8.4, and 9.7 release trains. No CWE is assigned, so the precise root cause class - whether resource exhaustion, null dereference, logic error, or input validation failure - is not publicly disclosed. Oracle's advisory language citing 'multiple protocols' is standard CPU boilerplate indicating the replication interface is reachable via MySQL's native protocol and potentially X Protocol. The hang-or-crash impact profile is consistent with an unhandled condition in replication message parsing or state management when processing attacker-supplied input.

RemediationAI

Apply the patches released as part of Oracle's July 2026 Critical Patch Update, available at https://www.oracle.com/security-alerts/cpujul2026.html. Exact patched build versions are not specified in the available data - consult Oracle's CPU patch matrix for the specific fixed build applicable to your MySQL Server or MySQL Cluster branch (8.0, 8.4, or 9.7). For MySQL Cluster, legacy 8.0.x deployments up to 8.0.47 require particular attention given the broader version range. As a compensating control where immediate patching is not feasible, restrict network access to MySQL replication ports (default 3306/TCP) to trusted hosts only via firewall rules, reducing the attack surface to adversaries already inside the trusted perimeter - note this may affect legitimate replica connectivity and must be coordinated with the replication topology. Additionally, audit and minimize accounts holding REPLICATION SLAVE, REPLICATION CLIENT, or SUPER privileges, since exploitation requires high-privilege credentials; revoking unnecessary grants eliminates the attacker's required foothold.