CVE-2025-13867: IBM Db2 for Linux, UNIX and Windows · Improper Validation of Specified Quantity in Input
Affects IBM Db2 for Linux, UNIX and WindowsSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| IBMDb2 for Linux, UNIX and Windows | Affected
| Fixed in– |
CPE configurations (20)
cpe:2.3:a:ibm:db2:11.5.0:*:*:*:*:linux:*:*cpe:2.3:a:ibm:db2:11.5.0:*:*:*:*:unix:*:*cpe:2.3:a:ibm:db2:11.5.0:*:*:*:*:aix:*:*cpe:2.3:a:ibm:db2:11.5.0:*:*:*:*:windows:*:*cpe:2.3:a:ibm:db2:11.5.0:*:*:*:*:zos:*:*cpe:2.3:a:ibm:db2:11.5.9:*:*:*:*:linux:*:*
AI-suggested
1. Restrict and audit authenticated user permissions to the minimum necessary, limiting access to trusted personnel only. 2. Implement robust monitoring and anomaly detection on database query patterns to identify unusual or malformed queries that could exploit this vulnerability. 3. Enforce strong authentication mechanisms and credential management to reduce the risk of compromised accounts being used to trigger the vulnerability. 4. Prepare for patch deployment by tracking IBM security advisories closely and testing updates in controlled environments before production rollout. 5. Consider temporary compensating controls such as query input validation proxies or database firewall rules to block suspicious query patterns if feasible. 6. Conduct regular security assessments and penetration tests focusing on database access controls and input validation mechanisms. 7. Educate database administrators and security teams about the vulnerability details and signs of exploitation attempts. 8. Maintain up-to-date backups and disaster recovery plans to minimize operational impact in case of successful denial of service attacks. These steps go beyond generic advice by focusing on access control tightening, proactive monitoring, and preparation for patch management specific to IBM Db2 environments.
Description
IBM 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