Db2Application · Ibm
CVE-2025-36122
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 using a specially crafted SQL query due to improper allocation of system 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-11.5.9 and 12.1.0-12.1.3 for Linux, UNIX, and Windows contains a vulnerability where an authenticated user can cause denial of service by executing specially crafted SQL queries that improperly allocate system resources, exhausting available memory or other system resources and rendering the database unavailable.
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.
-
Identify installed Db2 versionRun 'db2level' command from a Db2 instance owner account, or query DB2 GET VERSION using 'db2 get snapshot for database manager'Affected if Version is 11.5.0 through 11.5.9 or 12.1.0 through 12.1.3
-
Confirm operating system platformVerify the Db2 instance runs on Linux, UNIX, or Windows using 'uname -a' on Linux/UNIX or 'systeminfo' on WindowsAffected if Platform is Linux, UNIX, or Windows and version falls in affected range
-
Verify authentication is enabledCheck if Db2 authentication is configured: run 'db2 get dbm cfg | grep AUTHENTICATION'Affected if AUTHENTICATION is set to a value other than NONE, meaning users require authentication to connect
-
Check resource governor limitsRun 'db2 get resource limiter configuration' or inspect RESOURCE_USAGE_LMT configuration setting in dbm cfgAffected if No resource governor limits or memory limits are configured for user queries
-
Check query timeout settingsRun 'db2 get db cfg | grep QUERY_TIMEOUT' or check the QUERY_ELAPSE_TIME_BP settingAffected if Query timeout is not configured or set to unlimited (0), allowing long-running queries
User is affected if running Db2 11.5.0-11.5.9 or 12.1.0-12.1.3 on Linux/UNIX/Windows without enforced query timeouts or resource governor limits for authenticated users.
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 IBM's patched Db2 update (11.5.10 or 12.1.4 and later) to address the improper resource allocation. As a compensating control, consider implementing query timeouts or resource governor limits for authenticated users to mitigate exploitation while patching.
Fix this in Db2
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.0 h
- Testing6.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 $5,024.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36122 — 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-36122 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