dbcve.org
Mysql ServerDatabase / datastore · Oracle

CVE-2025-21497

MEDIUM · 5.5 CVSS v3.1 Published 2025-01-21
Fix available
A fix is available. Upgrade to after 9.1.0 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A vulnerability in the InnoDB storage engine of MySQL Server allows high-privileged attackers with network access to cause a denial of service (hang or crash) or achieve unauthorized data manipulation (insert/update/delete) on accessible data. The attack requires high privileges but can be exploited via multiple network protocols.

MitigationUpgrade MySQL Server to versions 8.0.41, 8.4.4, or 9.2.0 or later. Prior to upgrading in production, test the upgrade in a non-production environment to verify application compatibility.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mysql ServerDatabase / datastore
Affected:>= 8.0.0, <= 8.0.40>= 8.4.0, <= 8.4.3>= 9.0.0, <= 9.1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check MySQL Server version
    Run 'mysql --version' from command line or execute 'SELECT VERSION();' query against the MySQL instance
    Affected if The version falls within 8.0.0-8.0.40, 8.4.0-8.4.3, or 9.0.0-9.1.0
  2. Verify InnoDB storage engine is in use
    Execute 'SHOW ENGINES;' or 'SHOW VARIABLES LIKE 'default_storage_engine';' query. InnoDB is typically the default engine for MySQL 8.0 and later
    Affected if InnoDB is enabled as the storage engine (which is the default configuration)
  3. Confirm network exposure of MySQL service
    Check MySQL configuration for bind-address settings in my.cnf/my.ini or run 'SHOW VARIABLES LIKE 'bind_address';' to see what interfaces MySQL listens on
    Affected if MySQL is listening on a network interface accessible to attackers (0.0.0.0 or non-loopback IP)

A user is affected if their MySQL version is 8.0.0-8.0.40, 8.4.0-8.4.3, or 9.0.0-9.1.0, InnoDB storage engine is active, and the database is network-accessible to high-privileged attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 9.1.0
Interim mitigation

Upgrade MySQL Server to versions 8.0.41, 8.4.4, or 9.2.0 or later. Prior to upgrading in production, test the upgrade in a non-production environment to verify application compatibility.

Recommended fix High confidence

MySQL Server 8.0.41+ / 8.4.4+ / 9.2.0+

  1. 1. Determine your current MySQL Server version using: SELECT VERSION();
  2. 2. For MySQL 8.0.x users: Upgrade to MySQL Server 8.0.41 or later
  3. 3. For MySQL 8.4.x users: Upgrade to MySQL Server 8.4.4 or later
  4. 4. For MySQL 9.x users: Upgrade to MySQL Server 9.2.0 or later
  5. 5. Download the appropriate MySQL Server distribution from https://dev.mysql.com/downloads/mysql/
  6. 6. Follow standard MySQL upgrade procedures, typically using mysql_upgrade utility or in-place upgrade method
  7. 7. After upgrade, verify the new version and test application functionality
Caveat Review Oracle MySQL upgrade notes for potential incompatibilities; test in staging before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mysql Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-21497 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-21497 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data