MySQLDatabase / datastore · Oracle
CVE-2025-50076
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 · uneditedVulnerability in the MySQL Server product of Oracle MySQL (component: Server: DML). Supported versions that are affected are 8.0.0-8.0.25. 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 confidenceThis is a DML (Data Manipulation Language) component vulnerability in MySQL Server 8.0.x versions 8.0.0 through 8.0.25. A low-privileged attacker with network access via multiple protocols can exploit specially crafted DML statements to cause a denial of service via hang or repeatable crash of the MySQL Server.
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
>= 8.0.0, <= 8.0.42CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed MySQL Server versionRun 'mysql --version' or 'SELECT VERSION();' as a database user, or check the MySQL service version via package manager (rpm -q mysql-server, dpkg -l mysql-server)Affected if The version is 8.0.0 through 8.0.42 inclusive
-
Verify MySQL is listening on network interfacesCheck MySQL configuration files (my.cnf or my.ini) for 'bind-address' setting, or run 'netstat -tlnp | grep 3306' or 'ss -tlnp | grep 3306' to see if the port is bound to 0.0.0.0 or a non-localhost IPAffected if MySQL is bound to 0.0.0.0 or a routable IP address rather than 127.0.0.1 or localhost only
-
Confirm low-privileged user accounts exist with DML accessRun 'SELECT user, host, plugin FROM mysql.user;' to list users, then check privileges with 'SHOW GRANTS FOR 'user'@'host';' or query the mysql.user table for DML privileges (Select_priv, Insert_priv, Update_priv, Delete_priv)Affected if There are non-admin users with standard DML privileges granted who can connect remotely
-
Verify network accessibility of MySQL portFrom a remote host, attempt to reach the MySQL port (default 3306) using 'telnet <host> 3306' or 'nc -zv <host> 3306', or check firewall rules with 'iptables -L' or 'ufw status'Affected if The MySQL port is reachable from network segments containing untrusted users
The environment is affected if MySQL Server version 8.0.0 through 8.0.42 is running with network accessibility and low-privileged users have DML access over the network.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade MySQL Server to version 8.0.26 or later, or apply Oracle's corresponding quarterly security patch. Alternatively, restrict network access to the MySQL port and limit privileges of database users as a defense-in-depth measure.
MySQL 8.0.43 or later
- 1. Backup all MySQL databases before performing the upgrade
- 2. Review MySQL 8.0.43 release notes for any relevant changes to the DML component
- 3. Plan maintenance window as upgrade will require MySQL service restart
- 4. Test upgrade in non-production environment first
- 5. Execute upgrade to MySQL 8.0.43 or later following standard Oracle upgrade documentation
- 6. Verify MySQL service starts successfully post-upgrade
- 7. Run application smoke tests to confirm functionality
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
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-50076 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-50076 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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