CVE-2025-30695: Medium severity Oracle MySQL Server vulnerability

Published Apr 15, 2025
·
Updated

Last updated 5 May 2025

Other sources

Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB). Supported versions that are affected are 8.0.0-8.0.41, 8.4.0-8.4.4 and 9.0.0-9.2.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 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).

NVD

Affected Software

9 affected componentsFixes available
Oracle MySQL Server>=8.0.0<=8.0.41, >=8.4.0<=8.4.4, >=9.0.0<=9.2.0
debian/mysql-8.0
8.0.42-1
Oracle MySQL Server>=8.0.0<=8.0.41
Oracle MySQL Server>=8.4.0<=8.4.4
Oracle MySQL Server>=9.0.0<=9.2.0
Microsoft azl3 mysql 8.0.41-1<8.0.42-1
8.0.42-1
Microsoft cbl2 mysql 8.0.41-1<8.0.42-1
8.0.42-1
Microsoft azl3 mysql 8.0.42-1<8.0.42-1
8.0.42-1
Microsoft cbl2 mysql 8.0.42-1<8.0.42-1
8.0.42-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/mysql-8.0 to a version that resolves this vulnerability.

    Fixed in 8.0.42-1
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 8.0.42-1
  3. Upgrade

    Upgrade Oracle MySQL (InnoDB) to a version that resolves this vulnerability.

    Fixed in 8.0.41
  4. Upgrade

    Upgrade Oracle MySQL (InnoDB) to a version that resolves this vulnerability.

    Fixed in 8.4.4
  5. Upgrade

    Upgrade Oracle MySQL (InnoDB) to a version that resolves this vulnerability.

    Fixed in 9.2.0

Event History

Apr 15, 2025
CVE Published
via MITRE·08:31 PM
Data Sourced
via MITRE·08:31 PM
DescriptionSeverity
Data Sourced
via Red Hat·09:03 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·09:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
May 10, 2025
Data Sourced
via Ubuntu·12:08 AM
RemedyDescriptionSeverityAffected Software
Jun 23, 2025
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
SeverityAffected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity

Frequently Asked Questions

1

What is the severity of CVE-2025-30695?

CVE-2025-30695 has been classified as a high-severity vulnerability.

2

How do I fix CVE-2025-30695?

To fix CVE-2025-30695, update your MySQL Server to a version that is not affected, such as versions beyond 8.0.41, 8.4.4, or 9.2.0.

3

Who is affected by CVE-2025-30695?

CVE-2025-30695 affects users running MySQL Server versions 8.0.0 to 8.0.41, 8.4.0 to 8.4.4, and 9.0.0 to 9.2.0.

4

What type of attack can exploit CVE-2025-30695?

CVE-2025-30695 can be exploited by high-privileged attackers with network access through multiple protocols.

5

What component of MySQL Server is impacted by CVE-2025-30695?

CVE-2025-30695 specifically impacts the InnoDB component of the MySQL Server product.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203