CVE-2025-36006VulnerabilityPublished 7 Nov 2025

CVE-2025-36006: IBM Db2 · Improper Resource Shutdown or Release

Affects IBM Db2Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

6.5Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 23% 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 7 Nov 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 2026-10-26.

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 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
IBM Db2	Affected =10.5.0 =11.1.0 =11.5.0 =12.1.0	Fixed in–

AI-suggested

1. Monitor IBM’s security advisories closely and apply official patches or updates as soon as they become available to address CVE-2025-36006. 2. Restrict database access strictly to necessary authenticated users and enforce strong authentication mechanisms, including multi-factor authentication where possible. 3. Implement resource usage monitoring on Db2 servers to detect abnormal resource consumption patterns indicative of exploitation attempts. 4. Configure database and operating system resource limits (e.g., memory, file handles, connections) to prevent resource exhaustion from a single user or process. 5. Conduct regular audits of user privileges to minimize the number of users with sufficient rights to exploit this vulnerability. 6. Employ network segmentation and firewall rules to limit access to Db2 services only to trusted hosts and networks. 7. Prepare incident response plans that include steps to identify and mitigate denial of service conditions related to resource exhaustion. 8. Consider deploying application-layer protections or database activity monitoring tools that can alert on unusual behavior related to resource usage.

Description

CVE-2025-36006 is a medium severity vulnerability in IBM Db2 versions 10.5.0 through 12.1.3 that allows an authenticated user to cause a denial of service by improper resource shutdown or release. The flaw arises from the improper handling of resources after use, leading to potential resource exhaustion. Exploitation requires network access with low complexity and no user interaction, but does require authentication. The vulnerability impacts availability without affecting confidentiality or integrity. No known exploits are currently reported in the wild. European organizations using affected IBM Db2 versions should prioritize patching once available and monitor for unusual resource usage patterns.

Impact

For European organizations, the primary impact is on the availability of critical database services that IBM Db2 supports. Disruption of Db2 services can halt business operations, especially in sectors like finance, telecommunications, manufacturing, and government services where Db2 is commonly deployed. Denial of service can lead to operational downtime, loss of productivity, and potential financial losses. Since the vulnerability requires authentication, the risk is elevated in environments with weak access controls or compromised credentials. Additionally, prolonged resource exhaustion could affect other applications on shared infrastructure, amplifying the impact. Organizations with regulatory obligations for service availability and continuity, such as those under GDPR and NIS Directive, may face compliance risks if disruptions occur. The absence of known exploits reduces immediate risk but does not eliminate the threat, particularly as attackers may develop exploits once patches are released.

CWE-404Improper Resource Shutdown or Release (opens in a new tab)
Class weaknessLikelihood of exploit: Medium
The product does not release or incorrectly releases a resource before it is made available for re-use.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation
It is good practice to be responsible for freeing all resources you allocate and to be consistent with how and where you free memory in a function. If you allocate memory that you intend to free upon completion of the function, you must be sure to free the memory at all exit points for that function including error…
Implementation
Memory should be allocated/freed using matching functions such as malloc/free, new/delete, and new[]/delete[].
Attack patterns
TCP Fragmentation (opens in a new tab)
UDP Fragmentation (opens in a new tab)
ICMP Fragmentation (opens in a new tab)
BlueSmacking (opens in a new tab)
Flooding (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Nov 2025, 20:02 UTC

WeaknessesCWE-404

Technical details

References

Community reviews

Related threats