CVE-2025-36098: 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, 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 (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 resource usage closely on IBM Db2 servers to detect unusual spikes in CPU, memory, or connection usage that could indicate exploitation attempts. 2. Implement strict access controls and audit logging to limit and track authenticated user activities, reducing the risk of misuse by insiders or compromised accounts. 3. Apply network segmentation and firewall rules to restrict access to Db2 servers only to trusted hosts and users. 4. Enforce resource quotas or limits at the operating system or database configuration level where possible to prevent resource exhaustion. 5. Stay informed about IBM security advisories and apply official patches or updates promptly once released. 6. Conduct regular security assessments and penetration tests focusing on authentication mechanisms and resource management. 7. Prepare incident response plans specifically addressing database availability issues to minimize downtime impact. 8. Consider deploying database activity monitoring tools that can alert on anomalous resource consumption patterns.
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 could allow an authenticated user to cause a denial of service due to improper allocation of resources.