Skip to main content
CVE-2025-21497VulnerabilityPublished Updated

CVE-2025-21497: Oracle MySQL Server · Easily exploitable vulnerability allows high privileged attacker with network access via multiple

Affects Oracle MySQL ServerSource CVE Database V5

0

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Jan 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
Mavencom.oracle/mysql-serverpkg:maven/com.oracle/mysql-serverOther threatsAffected
  • <=8.0.40
  • <=8.4.3
  • <=9.1.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Apply official Oracle patches immediately once released for the affected MySQL Server versions. 2. Restrict network access to MySQL servers using firewalls and network segmentation, allowing only trusted hosts and services to connect. 3. Enforce the principle of least privilege by auditing and minimizing high-privileged user accounts and roles with network access to MySQL. 4. Implement strong authentication and authorization controls to prevent unauthorized privilege escalation. 5. Monitor database logs and network traffic for unusual activity indicative of exploitation attempts, such as repeated crashes or unauthorized data modification commands. 6. Consider deploying intrusion detection/prevention systems (IDS/IPS) tuned to detect anomalies in MySQL traffic. 7. Regularly back up databases and verify backup integrity to enable recovery in case of data corruption or service disruption. 8. Conduct security awareness training for database administrators and network operators about this vulnerability and secure configuration best practices.

Description

Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB). Supported versions that are affected are 8.0.40 and prior, 8.4.3 and prior and 9.1.0 and prior. 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 as well as unauthorized update, insert or delete access to some of MySQL Server accessible data. CVSS 3.1 Base Score 5.5 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H).

References

Community reviews

Loading reviews…