CVE-2025-2668: IBM Db2 for Linux, UNIX and Windows · Excessive Memory Allocation
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.3% chance of exploitation in 30 days – higher than 33% 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:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 30 Jan 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 (10)
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 tightly control authenticated user privileges to limit who can execute complex or resource-intensive queries on Db2 servers. 2. Implement query monitoring and anomaly detection to identify and block suspicious or unusually crafted queries that could trigger the vulnerability. 3. Employ network segmentation and access controls to reduce the attack surface and isolate critical database servers from less trusted networks or users. 4. Prepare for rapid deployment of patches or updates once IBM releases a fix; maintain close communication with IBM security advisories. 5. Regularly back up database configurations and data to enable quick recovery in case of service disruption. 6. Conduct internal penetration testing and vulnerability assessments focusing on authenticated user actions to detect potential exploitation paths. 7. Educate database administrators and security teams about this vulnerability and the importance of monitoring authenticated user activities. 8. Consider implementing rate limiting or resource quotas on query execution to prevent resource exhaustion scenarios. 9. Review and update incident response plans to include scenarios involving denial of service on critical database infrastructure.
Description
IBM Db2 for Linux, UNIX and Windows (includes Db2 Connect Server) 11.5.0 - 11.5.9 is vulnerable to a denial of service as the server may crash when an authenticated user creates a specially crafted query.