CVE-2025-36070: IBM Db2 for Linux, UNIX and Windows · Unthrottled Resource 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, 09:15 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 26 Oct 2026.
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. Monitor and analyze database query patterns to detect unusual or resource-intensive queries targeting specific table types. 2. Implement resource governance and query throttling mechanisms within Db2 to limit the impact of excessive resource consumption. 3. Restrict database access privileges to the minimum necessary, especially for users who can execute SELECT queries on sensitive or large tables. 4. Employ network segmentation and firewall rules to limit exposure of Db2 servers to untrusted networks. 5. Regularly review and audit database logs for signs of attempted exploitation or abnormal behavior. 6. Prepare for patch deployment by testing updates in controlled environments once IBM releases official fixes. 7. Consider deploying database high availability and failover solutions to minimize downtime in case of service disruption. 8. Educate database administrators and security teams about this vulnerability and the importance of proactive monitoring. 9. Use application-layer controls to validate and limit query complexity where possible. 10. Coordinate with IBM support for guidance and early access to patches or workarounds.
Description
IBM Db2 for Linux, UNIX and Windows (includes Db2 Connect Server) 11.5.0 - 11.5.9 and 12.1.0 - 12.1.3 is vulnerable to a denial of service as a trap may occur when selecting from certain types of tables.