Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-53067: Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. in Oracle Corporation MySQL Server

0
Medium
VulnerabilityCVE-2025-53067cvecve-2025-53067
Published: Tue Oct 21 2025 (10/21/2025, 20:03:05 UTC)
Source: CVE Database V5
Vendor/Project: Oracle Corporation
Product: MySQL Server

Description

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 9.0.0-9.4.0. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. 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).

AI-Powered Analysis

AILast updated: 10/28/2025, 21:16:00 UTC

Technical Analysis

CVE-2025-53067 is a vulnerability identified in Oracle MySQL Server versions 9.0.0 through 9.4.0, specifically within the Server Optimizer component. The flaw allows an attacker possessing high-level privileges and network access through multiple protocols to trigger a denial-of-service condition by causing the MySQL Server to hang or crash repeatedly. The vulnerability is classified under CWE-400, which relates to uncontrolled resource consumption leading to DoS. The CVSS 3.1 base score is 4.9, indicating a medium severity primarily due to its impact on availability (A:H) without affecting confidentiality or integrity. The attack vector is network-based (AV:N), with low attack complexity (AC:L), requiring high privileges (PR:H), and no user interaction (UI:N). The scope remains unchanged (S:U), meaning the impact is confined to the vulnerable component. No known exploits have been reported in the wild, and no patches have been released at the time of publication. This vulnerability could be exploited by insiders or attackers who have already gained elevated access, potentially disrupting database services critical to business operations.

Potential Impact

For European organizations, the primary impact of CVE-2025-53067 is the potential for denial-of-service attacks against MySQL Server instances, leading to service outages and operational disruptions. Organizations relying on MySQL for critical applications, including financial services, government databases, and e-commerce platforms, could experience downtime affecting business continuity and customer trust. While the vulnerability does not allow data theft or modification, the loss of availability can have cascading effects, such as delayed transactions, loss of revenue, and increased incident response costs. The requirement for high privileges limits the risk from external attackers but raises concerns about insider threats or compromised administrative accounts. Given the widespread use of MySQL in Europe, especially in sectors with stringent uptime requirements, this vulnerability poses a tangible risk to service reliability and operational resilience.

Mitigation Recommendations

To mitigate CVE-2025-53067, European organizations should implement strict network segmentation and access controls to limit high-privilege network access to MySQL servers. Employ role-based access control (RBAC) to minimize the number of users with elevated privileges. Monitor MySQL server logs and system metrics for signs of hangs or crashes indicative of exploitation attempts. Deploy intrusion detection systems (IDS) and anomaly detection tools tuned to identify unusual database behavior. Prepare incident response plans specifically addressing MySQL service disruptions. Until an official patch is released, consider deploying MySQL servers behind firewalls restricting access to trusted hosts and protocols. Regularly update and audit MySQL configurations to ensure adherence to security best practices. Engage with Oracle support channels to obtain timely patches and advisories. Additionally, consider implementing high-availability and failover mechanisms to reduce downtime impact in case of exploitation.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
oracle
Date Reserved
2025-06-24T16:45:19.424Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68f7e96f01721c03c6f13e3a

Added to database: 10/21/2025, 8:13:35 PM

Last enriched: 10/28/2025, 9:16:00 PM

Last updated: 10/30/2025, 2:10:14 PM

Views: 57

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats