Cyber Resilience

CVE-2025-36010

Ibm Db2 12.1.0 … 12.1.2

Published
29 July 2025
Modified
17 June 2026
Patch / advisory
View advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0024 15th percentile
Risk Priority 49 floored blend · peak EPSS

Summary

CVE-2025-36010 is a medium-severity Deadlock (CWE-833) vulnerability in Ibm Db2. Its CVSS base score is 6.5 (Medium).

Operationally, ranked at the 15th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

IBM Db2 for Linux 12.1.0, 12.1.1, and 12.1.2 could allow an unauthenticated user to cause a denial of service due to executable segments that are waiting for each other to release a necessary lock.

CWE(s)
CWE-833

Related Threats

CVEs Like This One

CVE-2024-25046Same product: Ibm Db2
CVE-2024-31881Same product: Ibm Db2
CVE-2025-36353Same product: Ibm Db2
CVE-2024-37071Same product: Ibm Db2
CVE-2026-10535Same product: Ibm Db2
CVE-2024-28762Same product: Ibm Db2
CVE-2025-36185Same product: Ibm Db2
CVE-2025-36186Same product: Ibm Db2
CVE-2025-36184Same product: Ibm Db2
CVE-2026-9762Same product: Ibm Db2

Affected Assets

ibm
db2
12.1.0, 12.1.1, 12.1.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V15.4.3

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation activities can exercise concurrent paths and resource contention to discover deadlock conditions before deployment.

SA-8 Security and Privacy Engineering Principles partial match

Security engineering principles applied during design can incorporate synchronization ordering, timeouts, and resource hierarchies that structurally avoid deadlock formation.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 partial match
prevents

Secure SDLC practices can include concurrency analysis and lock discipline to avoid deadlock conditions.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development can detect deadlock conditions through stress and concurrency testing.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle requires deadlock analysis and avoidance techniques during design and coding.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture principles include concurrency controls and resource-locking discipline that prevent deadlock.

A.8.28 Secure coding partial match
prevents

Secure coding standards mandate safe lock ordering, timeouts, and deadlock detection patterns.

A.8.32 Change management none match
none

Change management may catch deadlock-related defects during reviews but does not directly address concurrency design.

References