dbcve.org
Db2Application · Ibm

CVE-2025-13755

MEDIUM · 5.5 CVSS v3.1 Published 2026-05-26
Fix available
A fix is available. Upgrade to after 12.1.4 or later.
See remediation →
57/100
Remediation priority · Elevated
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 11.5.0 through 11.5.9, and 12.1.0 through 12.1.4 for Linux, UNIX and Windows (includes DB2 Connect Server) stores potentially sensitive information in log files that could be read by a local user.

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 confidence

IBM Db2 versions 11.5.0-11.5.9 and 12.1.0-12.1.4 on Linux, UNIX, and Windows platforms (including DB2 Connect Server) store potentially sensitive information in log files that can be read by any local user with filesystem access, resulting in information disclosure.

MitigationApply IBM's security patch or upgrade to a fixed Db2 version. Additionally, review and restrict log file permissions to limit read access to only authorized administrative users.

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:>= 11.5.0, <= 11.5.9>= 12.1.0, <= 12.1.4

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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. Check IBM Db2 installed version
    Run 'db2level' command or check Db2 installation directory for version information
    Affected if Version is 11.5.0 through 11.5.9, or 12.1.0 through 12.1.4
  2. Identify Db2 log file locations
    Run 'db2 get dbm cfg | grep DIAGPATH' to find the diagnostic path where log files are stored
    Affected if Log files exist in a directory that is accessible to all local users
  3. Verify log file permissions
    List files in the Db2 diagnostic directory (e.g., 'ls -la <diagpath>') and check if log files are readable by 'others' (e.g., permissions showing 'r--r--r--' or similar allowing world read)
    Affected if Log files have permissions that allow unprivileged users to read them (e.g., 'r--r--r--' or owner-read with world-readable group)

User is affected if IBM Db2 version is 11.5.0-11.5.9 or 12.1.0-12.1.4 AND log files in the Db2 diagnostic directory are readable by non-privileged local users.

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
Upgrade available Upgrade to a release after 12.1.4
Interim mitigation

Apply IBM's security patch or upgrade to a fixed Db2 version. Additionally, review and restrict log file permissions to limit read access to only authorized administrative users.

Fix this in Db2 Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA5.0 h
33.0 hours of engineering $5,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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