dbcve.org
Mysql ServerDatabase / datastore · Oracle

CVE-2025-21522

MEDIUM · 6.5 CVSS v3.1 Published 2025-01-21
Fix available
A fix is available. Upgrade to after 9.1.0 or later.
See remediation →
71/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: Server: Parser). 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 low 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 6.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 MySQL Server Parser component allows low-privileged attackers with network access to cause a denial of service via specially crafted SQL input, resulting in server hang or repeatable crashes.

MitigationApply Oracle's critical patch updates to upgrade MySQL Server to versions 8.0.41+, 8.4.4+, or 9.1.1+ respectively, or later supported versions.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Identify installed MySQL Server version
    Execute 'SELECT VERSION();' as any database user, or run 'mysqld --version' on the server host, or check the MySQL service version through your system's service manager
    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. Confirm MySQL network accessibility
    Check if the MySQL listener is bound to a network interface (0.0.0.0 or specific IP) by reviewing my.cnf/my.ini for 'bind-address' setting, or by running 'netstat -tlnp | grep 3306' or 'ss -tlnp | grep 3306'
    Affected if MySQL is listening on a reachable network address, making it exploitable via network access
  3. Verify the Parser component is in use
    The Parser is a core component of MySQL Server and is active for any SQL query processing; no additional configuration check is needed beyond confirming MySQL is running
    Affected if MySQL Server is running and accepting SQL queries, which inherently uses the Parser component

You are affected if your MySQL Server version is 8.0.0-8.0.40, 8.4.0-8.4.3, or 9.0.0-9.1.0 AND the server is accessible over the network, since the vulnerability is triggered by specially crafted SQL input sent by a low-privileged attacker with network access.

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

Apply Oracle's critical patch updates to upgrade MySQL Server to versions 8.0.41+, 8.4.4+, or 9.1.1+ respectively, or later supported versions.

Recommended fix High confidence

MySQL 8.0.41+ (8.0.x branch), MySQL 8.4.4+ (8.4.x branch), or MySQL 9.2.0+ (9.x branch)

  1. 1. Identify the current MySQL Server version using: `mysql --version` or `SELECT VERSION();`
  2. 2. Determine which version branch you are on (8.0.x, 8.4.x, or 9.x)
  3. 3. For MySQL 8.0.x users: Upgrade to MySQL 8.0.41 or later
  4. 4. For MySQL 8.4.x users: Upgrade to MySQL 8.4.4 or later
  5. 5. For MySQL 9.x users: Upgrade to MySQL 9.2.0 or later
  6. 6. Before upgrading in production, test the new version in a non-production environment
  7. 7. Perform a full backup of all databases before applying the upgrade
  8. 8. Stop the MySQL service, apply the upgrade, and restart the service
Caveat MySQL minor version upgrades within the same release series typically have minimal breaking changes, but review the release notes for any deprecation notices or behavioral changes between your current version and the target version before upgrading in production

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

Fix this in Mysql Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-21522 — 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-21522 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