CVE-2025-30722
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 Client product of Oracle MySQL (component: Client: mysqldump). Supported versions that are affected are 8.0.0-8.0.41, 8.4.0-8.4.4 and 9.0.0-9.2.0. Difficult to exploit vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Client. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all MySQL Client accessible data as well as unauthorized update, insert or delete access to some of MySQL Client accessible data. CVSS 3.1 Base Score 5.9 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N).
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 confidenceA vulnerability in the MySQL Client mysqldump utility allows a low-privileged attacker with network access to compromise the client through difficult-to-exploit attacks. Successful exploitation can result in unauthorized access to critical data or complete access to all MySQL Client accessible data, as well as unauthorized update, insert, or delete operations on some accessible data.
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>= 7.6.0, <= 7.6.33>= 8.0.0, <= 8.0.41>= 8.4.0, <= 8.4.4>= 9.0.0, <= 9.2.0>= 8.0.0, <= 8.0.41>= 8.4.0, <= 8.4.4>= 9.0.0, <= 9.2.0all versionsall versionsCVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
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 mysqldump versionRun 'mysqldump --version' or 'mysqldump -V' on the system to retrieve the installed mysqldump version numberAffected if The version displayed falls within 8.0.0-8.0.41, 8.4.0-8.4.4, or 9.0.0-9.2.0
-
Check Oracle MySQL Cluster versionRun 'mysql --version' or check the MySQL Cluster installation to determine the exact version numberAffected if The MySQL Cluster version is 7.6.0-7.6.33, 8.0.0-8.0.41, 8.4.0-8.4.4, or 9.0.0-9.2.0 and mysqldump is in use
-
Check NetApp Active IQ Unified ManagerLocate the bundled MySQL client libraries within the NetApp product installation directory and retrieve their version informationAffected if The product is any version of Active IQ Unified Manager and contains a MySQL client component in the affected version range
-
Check NetApp SnapCenterLocate the bundled MySQL client libraries within the NetApp product installation directory and retrieve their version informationAffected if The product is any version of SnapCenter and contains a MySQL client component in the affected version range
You are affected if mysqldump or any MySQL client component on your system reports a version within 8.0.0-8.0.41, 8.4.0-8.4.4, or 9.0.0-9.2.0, or if you run any version of NetApp Active IQ Unified Manager or SnapCenter that bundles MySQL client utilities.
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 · scopedApply Oracle's security patches by upgrading MySQL to a version beyond 8.0.41, 8.4.4, or 9.2.0 respectively. Since mysqldump is a client utility, ensure all client installations are updated in addition to server components.
MySQL 8.0.42, 8.4.5, 9.3.0, or Cluster 7.6.34 (depending on your major version line)
- 1. Identify current MySQL Client version using: mysql --version or mysqldump --version
- 2. For MySQL 8.0.x installations: Upgrade to MySQL 8.0.42 or later
- 3. For MySQL 8.4.x installations: Upgrade to MySQL 8.4.5 or later
- 4. For MySQL 9.x installations: Upgrade to MySQL 9.3.0 or later
- 5. For MySQL Cluster 7.6.x: Upgrade to MySQL Cluster 7.6.34 or later
- 6. For Active IQ Unified Manager and SnapCenter: Monitor vendor security advisories (NetApp) for specific patch availability
- 7. Verify upgrade success by running: mysql --version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30722 — 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-30722 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