VulnerabilityPublished 29 Jul 2025

CVE-2025-36010: IBM Db2 · Deadlock

Affects IBM Db2Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ibmibm/db2`pkg:rpm/ibm/db2`Other threats	Affected =12.1.0 =12.1.1 =12.1.2	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Given the absence of an official patch link, European organizations should implement the following specific mitigations: 1) Restrict network access to IBM Db2 instances by enforcing strict firewall rules and network segmentation to limit exposure to untrusted networks. 2) Monitor database logs and system performance metrics for signs of deadlock or unusual locking behavior that could indicate attempted exploitation. 3) Apply principle of least privilege to database users and services to minimize the ability of low-privilege accounts to trigger deadlocks. 4) Employ database connection throttling and query timeouts to reduce the risk of resource exhaustion caused by deadlock conditions. 5) Engage with IBM support to obtain any available patches or workarounds and plan for prompt deployment once released. 6) Conduct internal penetration testing and vulnerability scanning focused on deadlock scenarios to identify and remediate potential exploitation paths. 7) Maintain up-to-date backups and disaster recovery plans to mitigate the impact of potential service disruptions.

Description

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.

Impact

For European organizations, the impact of this vulnerability can be substantial, especially for those relying on IBM Db2 for critical business applications, financial systems, or government data processing. A successful exploitation leads to denial of service, which can cause downtime, disrupt business continuity, and potentially lead to financial losses or regulatory non-compliance due to service unavailability. Industries such as banking, telecommunications, healthcare, and public sector entities that use IBM Db2 databases could face operational disruptions. Since the vulnerability can be exploited remotely over the network with low privileges and no user interaction, it increases the risk of automated attacks or exploitation by insider threats. The lack of confidentiality or integrity impact reduces the risk of data breaches but does not diminish the operational risk posed by service outages. Additionally, the medium severity rating suggests that while the vulnerability is not critical, it requires timely attention to prevent potential exploitation.

References

ibm.com/support/pages/node/7240951 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Jul 2025, 18:32 UTC

WeaknessesCWE-833

Technical details

References

Community reviews

Related threats