CVE-2025-21525 is a vulnerability in Oracle MySQL Server affecting the Server: DDL component. Affected versions include 8.0.39 and earlier, 8.4.2 and earlier, and 9.0.1 and earlier. The flaw is described as easily exploitable by a high-privileged attacker with network access via multiple protocols. Successful exploitation can compromise MySQL Server availability by triggering a hang or a frequently repeatable crash, resulting in complete denial of service. The available information indicates an availability-focused server-side flaw in DDL processing, but does not provide sufficient technical detail about the specific vulnerable function or root cause to describe the internal code path with confidence.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.