CVE-2025-36122: IBM® Db2® is vulnerable to a denial of service with a specially crafted query when stmtheap is set to automatic
IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.3 for Linux, UNIX and Windows (includes DB2 Connect Server) could allow an authenticated user to cause a denial of service using a specially crafted SQL query due to improper allocation of system resources.
Security readout for executives and security teams
Plain-English summary
An authenticated Db2 user may be able to make affected IBM Db2 servers unavailable by running a specially crafted SQL query when statement heap memory is automatic. The issue affects availability only, but for business-critical databases that can still interrupt applications, reporting, or integrations.
Executive priority
Treat as a timely database availability risk, especially for production Db2 systems supporting critical services. It does not indicate data theft or tampering, but outage impact may justify prompt maintenance scheduling.
Technical view
CVE-2025-36122 is a CWE-770 improper resource allocation flaw in IBM Db2 for Linux, UNIX and Windows, including DB2 Connect Server. A network-accessible authenticated user with SQL execution capability can trigger denial of service. CVSS is 6.5 with high availability impact and no confidentiality or integrity impact.
Likely exposure
Exposure is most likely where IBM Db2 11.5.0 through 11.5.9 or 12.1.0 through 12.1.3 is deployed and stmtheap is set to automatic. Risk depends on who can authenticate and submit SQL queries.
Exploitation context
The provided sources do not show CISA KEV listing or confirmed active exploitation. Exploitation requires authentication, network access, and the ability to run a crafted SQL query. No exploit steps are provided here.
Researcher notes
The key exposure condition is authenticated SQL execution against affected Db2 versions with automatic stmtheap. Evidence in the bundle names a vendor advisory and patch reference, but does not include exploit details or exact fixed build mapping.
Mitigation direction
Review IBM advisory 7267642 for the supported fix path.
Apply the relevant IBM Db2 patch or fix pack.
Prioritize systems with automatic stmtheap configuration.
Restrict SQL access to trusted users and applications.
Monitor Db2 resource exhaustion and availability alerts.
Validation and detection
Inventory Db2 LUW and DB2 Connect Server versions.
Identify instances running 11.5.0-11.5.9 or 12.1.0-12.1.3.
Check whether stmtheap is configured as automatic.
Confirm IBM advisory fixes are installed.
Review logs for unexplained Db2 denial-of-service symptoms.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-770: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-770 · source CWE mapping
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.