Db2Application · Ibm
CVE-2025-36006
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 10.5.0 through 10.5.11, 11.1.0 through 11.1.4.7, 11.5.0 through 11.5.9, and 12.1.0 through 12.1.3 for Linux, UNIX and Windows (includes Db2 Connect Server) could allow an authenticated user to cause a denial due to the improper release of resources after use.
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 fails to properly release resources (likely memory or handles) after use by an authenticated user, leading to resource exhaustion and denial of service. This affects multiple major versions across Linux, UNIX, and Windows platforms.
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
>= 10.5.0.0, <= 10.5.0.11>= 11.1.0, <= 11.1.4.7>= 11.5.0, <= 11.5.9>= 12.1.0, <= 12.1.3CVSS 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 IBM Db2 is installedRun 'which db2' or 'which db2level' on Linux/UNIX, or check for Db2 installation directories on Windows (typically C:\Program Files\IBM\DB2 or similar). Also try executing 'db2level' from command line.Affected if Db2 binaries are found on the system
-
Determine installed Db2 versionExecute the 'db2level' command and note the output. On Windows, you may need to run this from a Db2 command window or use 'db2pd -version' from the bin directory.Affected if The displayed version falls within any of these ranges: 10.5.0.0-10.5.0.11, 11.1.0-11.1.4.7, 11.5.0-11.5.9, or 12.1.0-12.1.3
-
Confirm Db2 instance is runningRun 'db2 list active databases' or 'db2pd -db' to see if any Db2 instances are active. This vulnerability requires an authenticated user session to exploit.Affected if A Db2 instance is actively running and accepting authenticated connections
-
Check for resource exhaustion symptomsMonitor system resources while Db2 is running. On Linux/UNIX use 'top' or 'ps' to check memory usage of db2sysc processes. On Windows use Task Manager. Look for steadily increasing memory usage over time.Affected if Memory or handles are continuously increasing without being released during normal Db2 operations
A system is affected if IBM Db2 is installed with a version matching 10.5.0.0-10.5.0.11, 11.1.0-11.1.4.7, 11.5.0-11.5.9, or 12.1.0-12.1.3 and the database is actively running with authenticated user access.
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 appropriate IBM Db2 patch for your version (10.5.0-10.5.11, 11.1.0-11.1.4.7, 11.5.0-11.5.9, or 12.1.0-12.1.3). Until patched, monitor resource usage and limit database access to trusted authenticated users only.
Fix this in Db2
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36006 — 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-36006 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