CVE-2026-6052
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 running out of memory when executing certain queries with MDC 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 confidenceIBM Db2 versions 11.5.0 through 11.5.9 and 12.1.0 through 12.1.4 are vulnerable to memory exhaustion when executing certain queries against Multi-Dimensional Clustering (MDC) tables, potentially leading to denial of service conditions.
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 'db2level' command or query SELECT GET_VARCHAR_FOR_BIT_DATA(SERVICE_LEVEL) FROM SYSIBMADM.SYSENVIRONMENT. Compare the version number against the affected ranges: 11.5.0 through 11.5.9, and 12.1.0 through 12.1.4.Affected if The installed version falls within 11.5.0-11.5.9 or 12.1.0-12.1.4.
-
Confirm MDC tables existQuery the catalog: SELECT TABNAME FROM SYSCAT.TABLES WHERE TYPE='T' AND (DCOLUMNS IS NOT NULL OR (PROPERTY & 16) = 16). Alternatively, check if any tables were created with ORGANIZE BY DIMENSIONS clause.Affected if Any MDC tables exist in the database.
-
Check current memory consumptionMonitor memory usage via 'db2pd -mempool' or operating system tools (top, ps, vmstat) while queries on MDC tables are running. Look for unusually high memory usage by db2sysc process.Affected if Memory usage spikes significantly during MDC table queries.
-
Review query patterns against MDC tablesExamine active queries using 'db2pd -db <dbname> -applies' or query SYSCAT.STATEMENTS for frequently executed queries against tables identified in step 2.Affected if Queries are being executed against MDC tables.
If the Db2 version is within 11.5.0-11.5.9 or 12.1.0-12.1.4 AND MDC tables exist and are being queried, the environment is affected by this vulnerability.
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 vendor patch to upgrade to Db2 version 11.5.10 or 12.1.5. As an interim control, monitor memory usage and consider restricting or optimizing queries on MDC tables until the patch can be deployed.
- Consultation8.0 h
- Implementation12.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,048.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6052 — 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-6052 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