dbcve.org
Db2Application · Ibm

CVE-2025-36001

MEDIUM · 6.5 CVSS v3.1 Published 2026-01-30
Fix available
A fix is available. Upgrade to after 12.1.3 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click Patch available

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 for Linux, UNIX and Windows (includes Db2 Connect Server) 11.5.0 - 11.5.9 and 12.1.0 - 12.1.3 could allow an authenticated user to cause a denial of service using a specially crafted SQL statement including XML that performs uncontrolled recursion.

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

A detailed technical summary for this CVE is being prepared.

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.3

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
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

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 · scoped
Upgrade available Upgrade to a release after 12.1.3
Vendor patch www.ibm.com →
Recommended fix High confidence

Upgrade from 11.5.x to 11.5.10+ or from 12.1.x to 12.1.4+

  1. 1. Identify the current Db2 version by running: db2pd -version or SELECT GET_VARCHAR_FOR_BIT_DATA(COMPATIBLE_SPDB) FROM SYSIBM.SYSDUMMY1
  2. 2. Plan the upgrade based on your current version: if on 11.5.x, upgrade to 11.5.10 or later; if on 12.1.x, upgrade to 12.1.4 or later
  3. 3. Review IBM Db2 upgrade documentation for your specific version at https://www.ibm.com/docs/en/db2
  4. 4. Perform a full backup of all databases before upgrading
  5. 5. Stop all Db2 instances and services
  6. 6. Download the fixed Db2 version from IBM Fix Central or your authorized IBM distribution channel
  7. 7. Run the Db2 installer to apply the upgrade, following IBM's installation instructions
  8. 8. Start Db2 instances and verify all databases are accessible
Caveat Db2 upgrades may introduce compatibility changes; test applications in non-production environment before deploying to production

Generated from the published advisory — verify against the referenced sources before acting.

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-36001 — 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-2025-36001 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