dbcve.org
Db2Application · Ibm

CVE-2025-33114

HIGH · 7.5 CVSS v3.1 Published 2025-07-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 12.1.0, 12.1.1, and 12.1.2 is vulnerable to denial of service with a specially crafted query under certain non-default conditions.

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 confidence

IBM Db2 for Linux versions 12.1.0, 12.1.1, and 12.1.2 contains a denial of service vulnerability that can be triggered by a specially crafted SQL query when certain non-default configuration conditions are present, causing the database service to become unavailable.

MitigationApply IBM's Db2 patches for this vulnerability or upgrade to a version beyond 12.1.2; investigate and review non-default configuration settings that may contribute to exploitation.

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
Affected:= 12.1.0= 12.1.1= 12.1.2

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

Work through these to decide whether this CVE applies to you.

  1. Identify installed Db2 version
    Run 'db2level' or 'db2pd -versions' from a Db2 instance owner account to retrieve the installed Db2 version and build level
    Affected if The reported version is 12.1.0, 12.1.1, or 12.1.2
  2. Confirm version matches CVE scope
    Compare the version number from the previous step against the affected versions list (12.1.0, 12.1.1, 12.1.2)
    Affected if The version is exactly 12.1.0, 12.1.1, or 12.1.2
  3. Review non-default configuration settings
    Examine Db2 database manager configuration parameters using 'db2 get dbm cfg' and database configuration using 'db2 get db cfg' - look for any settings that deviate from IBM default values
    Affected if Non-default configuration settings are present alongside an affected version
  4. Test SQL query responsiveness
    Execute a simple SELECT query against the database to establish a baseline, then monitor for unexpected delays or failures
    Affected if Queries fail or timeout unexpectedly after a specially crafted SQL query is executed

A system is affected if it runs IBM Db2 version 12.1.0, 12.1.1, or 12.1.2 AND has non-default configuration settings present that could be exploited by a specially crafted SQL query.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply IBM's Db2 patches for this vulnerability or upgrade to a version beyond 12.1.2; investigate and review non-default configuration settings that may contribute to exploitation.

Fix this in Db2 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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