CVE-2026-6051
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 11.5.0 through 11.5.9, and 12.1.0 through 12.1.4 is vulnerable to a denial of service when executing a specially crafted query with a small statement heap.
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 confidenceIBM Db2 versions 11.5.0 through 11.5.9 and 12.1.0 through 12.1.4 contain a denial of service vulnerability. A remote attacker can execute a specially crafted query with a small statement heap to cause the database to become unavailable.
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>= 11.5.0, <= 11.5.9>= 12.1.0, <= 12.1.4CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 Db2 versionRun command: db2level or db2pd -version. On Linux/Unix you can also run: db2ls -a and check the installed path. Alternatively, connect to the database and run: SELECT GET_VARCHAR_FOR_BIT_DATA(PACKAGE_VERSION) AS VERSION FROM SYSIBM.SYSPACKAGE WHERE PKGNAME = 'NULLID' FETCH FIRST 1 ROW ONLY;Affected if The version command fails or returns no output, meaning Db2 may not be installed or the tools are not in PATH
-
Compare version against affected rangesParse the version number from step 1. For Db2 11.5.x, check if the minor version is between 0 and 9 inclusive. For Db2 12.1.x, check if the minor version is between 0 and 4 inclusive.Affected if The installed version is 11.5.0 through 11.5.9, or 12.1.0 through 12.1.4
-
Verify Db2 instance is runningRun: db2pd - on Linux/Unix check for running db2sysc processes, or on Windows check services for DB2-DB2COPY1 instance. Also can use: db2 list active databasesAffected if No Db2 instance is currently running, meaning the vulnerability is not currently exploitable against a live service
You are affected if the installed IBM Db2 version falls within 11.5.0-11.5.9 or 12.1.0-12.1.4 and the database instance is active.
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 dataUpgrade IBM Db2 to version 11.5.10 or later, or 12.1.5 or later. If immediate patching is not possible, restrict network access to the Db2 instance and monitor for anomalous query patterns.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6051 — 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-2026-6051 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