Db2Application · Ibm
CVE-2025-13867
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 for Linux, UNIX and Windows (includes Db2 Connect Server) 11.5.0 through 11.5.9 and 12.1.0 through 12.1.3 could allow an authenticated user to cause a denial of service due to improper neutralization of special elements in data query logic
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 confidenceIBM Db2 versions 11.5.0-11.5.9 and 12.1.0-12.1.3 contain a vulnerability where an authenticated user can trigger a denial of service via improper neutralization of special elements in data query logic, likely enabling injection-based attacks that cause the database to crash or become unresponsive.
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 Db2 version installedRun 'db2level' from a Db2 instance owner account or query 'SELECT SERVICE_LEVEL FROM SYSIBMADM.ENV_INST_INFO'Affected if Version is 11.5.0 through 11.5.9, or 12.1.0 through 12.1.3
-
Confirm instance service levelRun 'db2pd -version' or check the installation directory for version filesAffected if Service level matches vulnerable version ranges listed above
-
Verify Db2 is running and accessibleRun 'db2 connect to <database>' with any valid database credentialsAffected if Connection succeeds, confirming authenticated users can access the database
You are affected if your Db2 version is 11.5.0-11.5.9 or 12.1.0-12.1.3 and the database accepts authenticated user connections.
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 IBM Db2 vendor patches for versions 11.5.9 and 12.1.3 or later. Restrict database user privileges to minimum required and monitor for anomalous query patterns.
Db2 11.5.10 or later; Db2 12.1.4 or later
- Review the IBM Db2 upgrade documentation for your current version at https://www.ibm.com/docs/en/db2
- Ensure you have a complete backup of your database before upgrading
- Stop all Db2 instances and services
- For Db2 11.5.x users: Upgrade to Db2 version 11.5.10 or later
- For Db2 12.1.x users: Upgrade to Db2 version 12.1.4 or later
- After upgrade, verify the Db2 services start correctly
- Test critical database operations to confirm functionality
- Verify the vulnerability is resolved by checking Db2 version information using: db2pd -version or db2level
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
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13867 — 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-13867 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