Quick answers
- Is CVE-2025-36372 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-36372 being exploited in the wild.
- How severe is CVE-2025-36372?
- Medium severity, with a CVSS score of 5.5, published 30 June 2026.
- Which products and versions are affected?
- IBM DB2 Connect Server 11.5.0 - 11.5.9, 12.1.0 - 12.1.4; IBM Db2 for Linux, UNIX and Windows 11.5.0 - 11.5.9, 12.1.0 - 12.1.4.
- Is there a fix for CVE-2025-36372?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2025-36372 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2025-36372?
- Check whether you run IBM DB2 Connect Server, IBM Db2 for Linux or UNIX and Windows at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An information disclosure vulnerability exists in IBM Db2 for Linux, UNIX, and Windows (including Db2 Connect Server) versions 11.5 and 12.1. The flaw is categorized as CWE-538, where sensitive information is inserted into monitoring and event tables that are accessible to authenticated users. An attacker with local access and low privileges can exploit this by querying these tables to extract sensitive data. The vulnerability has a CVSS base score of 5.5, reflecting high confidentiality impact but no impact on integrity or availability. IBM has released special builds (interim fixes) for versions 11.5.9 and 12.1.4 to remediate the issue.
Affected products
- IBM Db2 for Linux, UNIX and Windows 11.5.0 - 11.5.9, 12.1.0 - 12.1.4
- IBM Db2 Connect Server 11.5.0 - 11.5.9, 12.1.0 - 12.1.4
Timeline
- 2026-06-23: disclosed: Initial publication by IBM
- 2026-06-25: advisory: Updated advisory to specify all platforms are impacted
- 2026-06-30: other: NVD publication date