CVE-2025-36008: IBM Db2 · Unthrottled Resource Allocation
Affects IBM Db2Source CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 23% 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 7 Nov 2025
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-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| IBM Db2 | Affected
| Fixed in– |
AI-suggested
European organizations should implement the following specific mitigations: 1) Monitor and audit database user activities to detect unusual resource consumption patterns indicative of exploitation attempts. 2) Enforce strict access controls and limit the number of users with authenticated access to Db2 instances, minimizing the attack surface. 3) Apply resource quotas or throttling mechanisms at the database or operating system level to prevent any single user from exhausting system resources. 4) Segregate critical database environments and implement network segmentation to reduce exposure. 5) Stay informed of IBM security advisories and apply patches or updates promptly once released. 6) Use multi-factor authentication to reduce the risk of credential compromise. 7) Conduct regular vulnerability assessments and penetration testing focused on resource exhaustion scenarios. 8) Prepare incident response plans specifically addressing denial of service conditions affecting database availability.
Description
IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.3 for Linux, UNIX and Windows (includes Db2 Connect Server) could allow an authenticated user to cause a denial of service due to improper allocation of resources.