Skip to main content
CVE-2025-36424VulnerabilityPublished Updated

CVE-2025-36424: IBM Db2 for Linux, UNIX and Windows · Improper Validation of Specified Quantity in Input

Affects IBM Db2 for Linux, UNIX and WindowsSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium.

Data as of 25 Oct 2026, 19:02 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jan 2026

  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-25.

What to do

Affected software

ProductAffectedFixed in
IBMDb2 for Linux, UNIX and WindowsAffected
  • >=11.5.0 <=11.5.9
  • >=12.1.0 <=12.1.3
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 IBM’s official security advisories closely and apply patches or updates as soon as they become available for affected Db2 versions (11.5.0 and 12.1.0). 2. Implement strict database user privilege management to ensure that users have only the minimum necessary permissions, reducing the risk of exploitation by low-privilege users. 3. Employ query input validation and anomaly detection mechanisms to identify and block suspicious or malformed queries that could trigger the vulnerability. 4. Use network segmentation and firewall rules to limit access to Db2 servers only to trusted hosts and users. 5. Enable detailed logging and monitoring of database activities to detect unusual patterns indicative of exploitation attempts. 6. Conduct regular security audits and penetration testing focused on database security to identify and remediate potential weaknesses. 7. Educate database administrators and security teams about this vulnerability and the importance of credential security to prevent insider threats or credential compromise.

Description

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

References

Community reviews

Loading reviews…