CVE-2026-18097: CWE-532 Insertion of Sensitive Information into Log File in IBM Db2
IBM Db2 versions 11.5.0 through 11.5.9 and 12.1.0 through 12.1.5 for Linux, UNIX, and Windows may log plaintext passwords in trace files. This vulnerability could allow a local attacker with access to these files to obtain sensitive information. The issue is classified under CWE-532, which involves the insertion of sensitive information into log files. The vulnerability has a medium severity with a CVSS score of 5.5. No official patch or remediation guidance has been provided yet.
AI Analysis
Technical Summary
CVE-2026-18097 describes a vulnerability in IBM Db2 where plaintext passwords are logged in trace files, potentially exposing sensitive credentials to local attackers. Affected versions include 11.5.0 through 11.5.9 and 12.1.0 through 12.1.5 on Linux, UNIX, and Windows platforms, including DB2 Connect Server. The vulnerability is due to improper handling of sensitive information in logs (CWE-532). The CVSS v3.1 base score is 5.5, reflecting a medium severity with local attack vector and low attack complexity, requiring low privileges and no user interaction. There is no known exploit in the wild and no official remediation level or patch has been disclosed at this time.
Potential Impact
Local attackers with access to the system could retrieve plaintext passwords from Db2 trace log files, leading to potential credential compromise. This exposure affects confidentiality but does not impact integrity or availability. The vulnerability requires local access and low privileges but no user interaction.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, restrict access to Db2 trace files to trusted administrators only and monitor for unauthorized local access. Avoid enabling verbose logging that may include sensitive information if possible.
CVE-2026-18097: CWE-532 Insertion of Sensitive Information into Log File in IBM Db2
Description
IBM Db2 versions 11.5.0 through 11.5.9 and 12.1.0 through 12.1.5 for Linux, UNIX, and Windows may log plaintext passwords in trace files. This vulnerability could allow a local attacker with access to these files to obtain sensitive information. The issue is classified under CWE-532, which involves the insertion of sensitive information into log files. The vulnerability has a medium severity with a CVSS score of 5.5. No official patch or remediation guidance has been provided yet.
CVSS v3.1
Score 5.5medium
Affected software
cpe:2.3:a:ibm:db2:11.5.0:*:*:*:*:*:*:*cpe:2.3:a:ibm:db2:11.5.9:*:*:*:*:*:*:*cpe:2.3:a:ibm:db2:12.1.0:*:*:*:*:*:*:*cpe:2.3:a:ibm:db2:12.1.5:*:*:*:*:*:*:*Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-18097 describes a vulnerability in IBM Db2 where plaintext passwords are logged in trace files, potentially exposing sensitive credentials to local attackers. Affected versions include 11.5.0 through 11.5.9 and 12.1.0 through 12.1.5 on Linux, UNIX, and Windows platforms, including DB2 Connect Server. The vulnerability is due to improper handling of sensitive information in logs (CWE-532). The CVSS v3.1 base score is 5.5, reflecting a medium severity with local attack vector and low attack complexity, requiring low privileges and no user interaction. There is no known exploit in the wild and no official remediation level or patch has been disclosed at this time.
Potential Impact
Local attackers with access to the system could retrieve plaintext passwords from Db2 trace log files, leading to potential credential compromise. This exposure affects confidentiality but does not impact integrity or availability. The vulnerability requires local access and low privileges but no user interaction.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, restrict access to Db2 trace files to trusted administrators only and monitor for unauthorized local access. Avoid enabling verbose logging that may include sensitive information if possible.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- ibm
- Date Reserved
- 2026-07-28T17:15:50.150Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a7ce1eabf8831d5392b0331
Added to database: 08/12/2026, 21:13:14 UTC
Last enriched: 08/12/2026, 21:28:33 UTC
Last updated: 08/12/2026, 22:41:41 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.