Skip to main content
CVE-2025-36185VulnerabilityPublished

CVE-2025-36185: IBM Db2 · Improper Neutralization of Special Elements in Data Query Logic

Affects IBM Db2Source CVE Database V5

0

Not known to be exploited · CVSS 6.2 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
6.2Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 3% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
IBM Db2Affected
  • =12.1.0
Fixed in–

AI-suggested

1. Restrict local access to IBM Db2 servers strictly to trusted administrators and service accounts; implement strong access controls and user authentication. 2. Employ network segmentation and host-based firewalls to limit lateral movement and reduce the risk of attackers gaining local access. 3. Monitor database logs and system behavior for unusual query patterns or signs of resource exhaustion that could indicate exploitation attempts. 4. Apply principle of least privilege to all users and processes interacting with Db2 to minimize potential attack vectors. 5. Stay informed of IBM security advisories and apply official patches or updates promptly once released to address this vulnerability. 6. Consider implementing runtime protections or database activity monitoring tools that can detect and block malformed queries targeting this vulnerability. 7. Conduct regular security audits and penetration testing focusing on local access controls and database query handling. 8. Prepare incident response plans to quickly isolate and recover from potential denial of service events affecting Db2 services.

Description

IBM Db2 12.1.0 through 12.1.2 for Linux, UNIX and Windows (includes Db2 Connect Server) could allow a local user to cause a denial of service due to improper neutralization of special elements in data query logic.

References

Community reviews

Loading reviews…