dbcve.org
Db2Application · Ibm

CVE-2026-6053

MEDIUM · 5.5 CVSS v3.1 Published 2026-05-27
Fix available
A fix is available. Upgrade to after 12.1.4 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.4 is vulnerable to a denial of service when a specially crafted query is run with range partitioned tables.

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 confidence

IBM Db2 versions 11.5.0 through 11.5.9 and 12.1.0 through 12.1.4 contain a denial of service vulnerability triggered by specially crafted queries executed against range partitioned tables, causing the database service to become unresponsive or crash.

MitigationApply IBM's published Db2 fix packs or upgrade to a patched version beyond 11.5.9 and 12.1.4 to address the vulnerability.

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
Db2Application
Affected:>= 11.5.0, <= 11.5.9>= 12.1.0, <= 12.1.4

CVSS 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Db2 version
    Run 'db2level' command from a Db2 instance administrator account, or query SELECT GET_VARS FOR VARIABLE ('DB2_VERSION') FROM SYSIBM.SYSDUMMY1
    Affected if The version returned is 11.5.0 through 11.5.9 or 12.1.0 through 12.1.4
  2. Check for range partitioned tables in the database
    Query the system catalog: SELECT TABSCHEMA, TABNAME FROM SYSCAT.TABLES WHERE TABSCHEMA NOT LIKE 'SYS%' with additional check: SELECT * FROM SYSCAT.PARTITIONEXPRS WHERE (condition to identify range partitioning). Alternatively, check if any tables were created using PARTITION BY RANGE clause.
    Affected if Any range partitioned tables exist in the database
  3. Verify database is accessible for query execution
    Confirm database is online and accepting connections. Run 'db2 list database directory' to list accessible databases and 'db2 connect to <database>' to verify connectivity.
    Affected if The database is online and accessible (the vulnerability is only triggerable when queries can be executed against affected tables)

A user is affected if they are running a Db2 version in the 11.5.0-11.5.9 or 12.1.0-12.1.4 range AND have range partitioned tables in their database that could accept specially crafted queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 12.1.4
Interim mitigation

Apply IBM's published Db2 fix packs or upgrade to a patched version beyond 11.5.9 and 12.1.4 to address the vulnerability.

Fix this in Db2 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6053 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-6053 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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