Db2 Merge BackupApplication · Ibm
CVE-2025-33130
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 · uneditedIBM DB2 Merge Backup for Linux, UNIX and Windows 12.1.0.0 could allow an authenticated user to cause the program to crash due to a buffer being overwritten when it is allocated on the stack.
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 · moderate confidenceIBM DB2 Merge Backup version 12.1.0.0 for Linux, UNIX, and Windows contains a stack-based buffer overflow vulnerability that allows an authenticated user to overwrite a buffer allocated on the stack, causing the program to crash (denial of service).
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
Db2 Merge BackupApplication
= 12.1.0.0CVSS 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.
-
Verify DB2 is installedRun command: db2level or db2pd -version. If command not found, DB2 may not be installed.Affected if DB2 is not installed, the vulnerability does not apply
-
Check DB2 versionRun: db2level or db2pd -versions. Look for version 12.1.0.0 in the output.Affected if The installed DB2 version is exactly 12.1.0.0, matching the affected version
-
Confirm Merge Backup feature presenceCheck if Merge Backup is available by running: db2pd -db <dbname> | grep -i merge, or inspect DB2 configuration for merge backup related entries. Also check: db2 get dbm cfg | grep -i mergeAffected if Merge Backup feature is present and configured in the DB2 environment
-
Review DB2 diagnostic logs for crashesExamine DB2 diagnostic logs in the diagnostic directory (default: sqllib/db2dump). Look for stack traces or crash events related to db2merge or merge backup operations: db2diag -A -g <timestamp> | grep -i crash or review db2diag.log entries with 'Signal' or 'stack'Affected if Recent crash events or stack traces in db2diag logs involving merge backup processes are found
A user is affected if DB2 version 12.1.0.0 is installed AND the Merge Backup feature is present and in use in their environment.
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.
From vendor dataApply the IBM-supplied patch for this vulnerability. Until patch deployment, restrict access to trusted authenticated users only and monitor for crash events in DB2 Merge Backup processes.
Fix this in Db2 Merge Backup
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-33130 — 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-33130 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