Skip to main content
VulnerabilityPublished

CVE-2025-36425: IBM Db2 for Linux, UNIX and Windows · CWE-256

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

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Feb 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 official channels for patches addressing CVE-2025-36425 and apply them promptly once released.
  2. Restrict database user privileges rigorously, ensuring that users have only the minimum necessary permissions, especially in environments using HADR.
  3. Review and harden HADR configurations to minimize exposure of sensitive information, including auditing replication and failover settings.
  4. Implement network segmentation and access controls to limit which authenticated users can connect to the database servers, reducing the risk of lateral movement.
  5. Employ strong authentication mechanisms and monitor for unusual access patterns or privilege escalations within the database environment.
  6. Conduct regular security audits and vulnerability assessments focusing on database configurations and user permissions.
  7. Encrypt sensitive data at rest and in transit within the database and HADR channels to reduce the impact of potential data exposure.
  8. Educate internal teams about the risks of insider threats and enforce strict credential management policies.

Description

IBM Db2 for Linux, UNIX and Windows (includes Db2 Connect Server) 11.5.0 through 11.5.9 and 12.1.0 through 12.1.3 could allow an authenticated user to obtain sensitive information under specific HADR configuration.

References

Community reviews

Loading reviews…