CVE-2026-18097: IBM Db2 · Sensitive Data in Logs
Affects IBM Db2Source CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 11 Nov 2026, 23:24 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 12 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| IBMDb2 | Affected
| Fixed in– |
CPE configurations (4)
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:*:*:*:*:*:*:*
AI-suggested
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.
Description
IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 for Linux, UNIX and Windows (includes DB2 Connect Server) could allow a local attacker to obtain sensitive information due to the logging of plain text passwords in trace files.