CVE-2025-36353: IBM Db2 for Linux, UNIX and Windows · CWE-943
Affects IBM Db2 for Linux, UNIX and WindowsSource CVE Database V5
Not known to be exploited · CVSS 6.2 Medium.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/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. Restrict local access to servers running IBM Db2 to trusted administrators and processes only, minimizing the risk of exploitation by unauthorized local users. 2. Implement strict access controls and monitoring on database hosts to detect unusual query patterns or resource usage indicative of exploitation attempts. 3. Employ host-based intrusion detection systems (HIDS) and security information and event management (SIEM) tools to alert on suspicious activities related to Db2 processes. 4. Segregate database servers in secure network zones with limited user access to reduce the attack surface. 5. Regularly audit user accounts and permissions on database hosts to ensure no unauthorized local accounts exist. 6. Stay informed on IBM security advisories and apply patches or updates promptly once they become available for this vulnerability. 7. Consider temporary workarounds such as disabling or limiting certain query functionalities if feasible, until patches are released. 8. Conduct internal penetration testing and vulnerability assessments focusing on local privilege escalation and DoS scenarios involving Db2.
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 a local user to cause a denial of service due to improper neutralization of special elements in data query logic.