CVE-2025-21523
First published: Tue Jan 21 2025(Updated: )
Last updated 30 January 2025
Credit: secalert_us@oracle.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| debian/mysql-8.0 | 8.0.41-2 | |
| MySQL Server | <8.0.40<8.4.3<9.1.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://www.oracle.com/security-alerts/cpujan2025.html
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21523
- https://nvd.nist.gov/vuln/detail/CVE-2025-21523
- https://launchpad.net/bugs/cve/CVE-2025-21523
- https://security-tracker.debian.org/tracker/CVE-2025-21523
- https://ubuntu.com/security/CVE-2025-21523
Frequently Asked Questions
What is the severity of CVE-2025-21523?
CVE-2025-21523 is classified as a high severity vulnerability due to its potential for exploitation by high privileged users.
How do I fix CVE-2025-21523?
To fix CVE-2025-21523, upgrade your MySQL Server to version 8.0.41-2 or later.
Which MySQL versions are affected by CVE-2025-21523?
CVE-2025-21523 affects MySQL versions 8.0.40 and prior, 8.4.3 and prior, and 9.1.0 and prior.
Is CVE-2025-21523 an exploit that needs network access?
Yes, CVE-2025-21523 requires network access for exploitation.
What component of MySQL Server does CVE-2025-21523 impact?
CVE-2025-21523 impacts the InnoDB component of MySQL Server.
- collector/mitre-cve
- source/MITRE
- agent/type
- agent/first-publish-date
- agent/author
- agent/severity
- collector/epss-latest
- source/FIRST
- agent/epss
- collector/usn-cve
- source/Ubuntu
- agent/references
- agent/source
- agent/description
- collector/nvd-api
- source/NVD
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- agent/last-modified-date
- agent/weakness
- agent/tags
- agent/softwarecombine
- agent/event
- collector/security-tracker-debian
- source/Debian
- vendor/oracle
- canonical/mysql server
- package-manager/debian