CVE-2025-36387

CVE-2025-36387 is a medium-severity vulnerability in Ibm Db2 with a CVSS 3.x base score of 6.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-770.

Key facts

Description

IBM Db2 for Linux, UNIX and Windows (includes DB2 Connect Server) 11.5.0 - 11.5.9 could allow an authenticated user to cause a denial of service when given specially crafted query.

Frequently asked questions

What is CVE-2025-36387?
IBM Db2 for Linux, UNIX and Windows (includes DB2 Connect Server) 11.5.0 - 11.5.9 could allow an authenticated user to cause a denial of service when given specially crafted query.
How severe is CVE-2025-36387?
CVE-2025-36387 has a CVSS 3.x base score of 6.5, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2025-36387 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (25th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-36387?
CVE-2025-36387 primarily affects Ibm Db2. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2025-36387?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-36387 have an EU (EUVD) identifier?
Yes. CVE-2025-36387 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-206561.
When was CVE-2025-36387 published?
CVE-2025-36387 was published on 2026-01-30 and last updated on 2026-06-17.

References

Affected products (3)

More vulnerabilities in Ibm Db2

All CVEs affecting Ibm Db2 →

Other CWE-770 (Allocation of Resources Without Limits or Throttling) vulnerabilities

Browse all CWE-770 (Allocation of Resources Without Limits or Throttling) vulnerabilities →