Skip to main content
VulnerabilityPublished Updated

CVE-2025-36009: 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 26 Oct 2026, 10:12 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 32% 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 26 Oct 2026.

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. Restrict and monitor authenticated user privileges to limit access to trusted personnel only, reducing the risk of exploitation.
  2. Implement robust credential management and multi-factor authentication to prevent unauthorized access.
  3. Monitor database server resource usage and logs for unusual spikes or patterns indicative of exploitation attempts targeting the global variable.
  4. Apply any IBM-provided patches or updates promptly once available.
  5. Consider deploying rate limiting or input validation controls at application or middleware layers to prevent excessive input quantities reaching the database.
  6. Conduct regular security audits and vulnerability assessments focused on database configurations and user permissions.
  7. Prepare incident response plans to quickly restore service in case of denial of service events.
  8. Engage with IBM support for guidance and early access to fixes or workarounds.

Description

IBM Db2 for Linux, UNIX and Windows (includes DB2 Connect Server) could allow an authenticated user to cause a denial of service due to excessive use of a global variable.

References

Community reviews

Loading reviews…