Skip to main content
VulnerabilityPublished Updated

CVE-2025-36407: 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, 17:16 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 23% 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. Monitor IBM’s security advisories closely and apply patches or updates for Db2 versions 11.5.0 and 12.1.0 as soon as they become available.
  2. Restrict ALTER TABLE permissions strictly to trusted database administrators to minimize the attack surface.
  3. Implement network segmentation and firewall rules to limit access to Db2 servers only to authorized users and systems.
  4. Employ database activity monitoring tools to detect unusual ALTER TABLE queries or patterns indicative of exploitation attempts.
  5. Conduct regular security audits and vulnerability assessments on database environments to identify and remediate configuration weaknesses.
  6. Consider deploying failover and high availability configurations to reduce downtime impact in case of a DoS event.
  7. Educate database administrators on secure query practices and the risks associated with schema modification commands.
  8. If possible, temporarily disable or limit ALTER TABLE operations during periods of heightened threat until patches are applied.

Description

IBM® Db2® is vulnerable to a denial of service with a specially crafted query that uses ALTER TABLE operations.

References

Community reviews

Loading reviews…