dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2025-50078

MEDIUM · 6.5 CVSS v3.1 Published 2025-07-15
Fix available
A fix is available. Upgrade to after 9.3.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: DML). Supported versions that are affected are 8.0.0-8.0.42, 8.4.0-8.4.5 and 9.0.0-9.3.0. 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

Vulnerability in MySQL Server's DML (Data Manipulation Language) component allows low-privileged users with network access to cause denial of service via specially crafted SQL statements. Successful exploitation results in MySQL Server hangs or repeatable crashes.

MitigationApply Oracle MySQL security patches to upgrade to a version beyond the affected versions (8.0.43+, 8.4.6+, 9.0.1+). Implement network access controls to limit which users can submit DML queries.

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
MySQLDatabase / datastore
Affected:>= 8.0.0, <= 8.0.42>= 8.4.0, <= 8.4.5>= 9.0.0, <= 9.3.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. Check MySQL Server version
    Run `SELECT VERSION();` or `mysql --version` to retrieve the installed MySQL version number
    Affected if The version falls within >= 8.0.0 and <= 8.0.42, OR >= 8.4.0 and <= 8.4.5, OR >= 9.0.0 and <= 9.3.0
  2. Verify network listener is enabled
    Check the MySQL configuration file (my.cnf or my.ini) for `bind-address` setting or run `SHOW VARIABLES LIKE 'bind_address';` to see if network listening is active
    Affected if Network listening is enabled and the server is reachable over the network
  3. Confirm low-privileged user access
    Review user accounts with `SELECT user, host FROM mysql.user;` and check their privileges with `SHOW GRANTS FOR 'username'@'host';` to identify accounts with limited privileges that can connect remotely
    Affected if There are low-privileged user accounts with network (remote) access permissions (e.g., user@'%' or user@'<external_ip>')
  4. Check DML access for remote users
    For each remote-access low-privileged user, verify they have any DML permissions (SELECT, INSERT, UPDATE, DELETE) on any database using `SHOW GRANTS;` and database-specific `SHOW GRANTS;`
    Affected if Remote low-privileged users have DML permissions on any database

The environment is affected if MySQL Server version is 8.0.0-8.0.42, 8.4.0-8.4.5, or 9.0.0-9.3.0 AND the server allows network access from low-privileged users who can execute DML statements.

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.3.0
Interim mitigation

Apply Oracle MySQL security patches to upgrade to a version beyond the affected versions (8.0.43+, 8.4.6+, 9.0.1+). Implement network access controls to limit which users can submit DML queries.

Recommended fix Moderate confidence

MySQL 8.0.43+ / 8.4.6+ / 9.3.1+ (depending on your current major version)

  1. 1. Backup your MySQL database before performing any upgrade
  2. 2. Schedule a maintenance window as upgrades require server restart
  3. 3. For MySQL 8.0.x: Upgrade to MySQL 8.0.43 or later
  4. 4. For MySQL 8.4.x: Upgrade to MySQL 8.4.6 or later
  5. 5. For MySQL 9.x: Upgrade to MySQL 9.3.1 or later
  6. 6. Download the appropriate MySQL Server package from https://dev.mysql.com/downloads/mysql/
  7. 7. Stop the MySQL Server service
  8. 8. Install the new MySQL Server version
Caveat In-place upgrades between minor versions are generally safe, but always test your application against the new version in a staging environment first; review MySQL release notes for any behavior changes

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

Fix this in MySQL Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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