Db2Application · Ibm
CVE-2025-36008
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.3 for Linux, UNIX and Windows (includes Db2 Connect Server) could allow an authenticated user to cause a denial of service due to improper allocation of resources.
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.3 for Linux, UNIX, and Windows contain a vulnerability where an authenticated user can exhaust server resources due to improper allocation, causing 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
Db2Application
>= 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.
-
Check IBM Db2 installed versionRun the command `db2level` or `db2pd -version` from a Db2 instance owner account to retrieve the installed version numberAffected if The displayed version falls within 11.5.0 to 11.5.9 or 12.1.0 to 12.1.3
-
Confirm Db2 edition and platformVerify the output shows Db2 running on Linux, UNIX, or Windows platforms using the platform information from `db2level`Affected if The platform is Linux, UNIX, or Windows and the version matches the affected ranges
-
Check if instance is runningRun `db2 list applications` or check the Db2 service status to confirm an active instance existsAffected if An active Db2 instance is running, making the resource exhaustion vulnerability exploitable
A user is affected if they have IBM Db2 version 11.5.0-11.5.9 or 12.1.0-12.1.3 running on Linux, UNIX, or Windows, since an authenticated user could trigger the resource exhaustion.
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.
dbcve · scopedApply the IBM Db2 security patch or upgrade to a patched version as specified in IBM's security bulletin.
Db2 11.5.10 or later; Db2 12.1.4 or later (choose the appropriate branch based on your current major version)
- 1. Identify your current IBM Db2 version by running 'db2level' command or checking via DB2 Administration Tool
- 2. Plan maintenance window for Db2 upgrade - this requires database downtime
- 3. Back up all databases before performing upgrade
- 4. Download the appropriate Db2 fix pack from IBM Fix Central (https://www.ibm.com/support/fixcentral/)
- 5. Stop all Db2 instances and dependencies before applying the upgrade
- 6. Apply Db2 11.5.10 or later (for 11.5.x branch), or Db2 12.1.4 or later (for 12.1.x branch)
- 7. Start Db2 instances and verify all databases are accessible
- 8. Run validation queries to confirm normal database operations
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Db2
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36008 — 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-36008 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