Skip to main content
VulnerabilityPublished Updated

CVE-2025-36427: 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, 14:05 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 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–
Ibmibm/db2pkg:rpm/ibm/db2Other threatsAffected
  • =11.5.0
  • =12.1.0
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:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should implement the following specific mitigations: 1) Monitor IBM’s security advisories closely and apply patches or updates as soon as IBM releases them for affected Db2 versions. 2) Restrict database access strictly to trusted and authorized users, employing network segmentation and firewall rules to limit exposure. 3) Enforce the principle of least privilege for database users to reduce the risk of exploitation by limiting who can execute complex queries. 4) Implement query monitoring and anomaly detection to identify unusual or malformed queries that could indicate exploitation attempts. 5) Regularly audit database logs and user activities for signs of suspicious behavior. 6) Consider deploying database activity monitoring (DAM) solutions that can alert on abnormal query patterns. 7) In environments where patching is delayed, consider temporary compensating controls such as disabling or restricting features that process special elements in queries if feasible. 8) Educate database administrators and security teams about this vulnerability and response procedures.

Description

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

References

Community reviews

Loading reviews…