CVE-2025-13108VulnerabilityPublished 17 Feb 2026Updated 26 Feb 2026

CVE-2025-13108: IBM DB2 Merge Backup for Linux, UNIX and Windows · Vulnerability

Affects IBM DB2 Merge Backup for Linux, UNIX and WindowsSource CVE Database V5

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.5Medium

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

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

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

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

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

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Feb 2026
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
IBMDB2 Merge Backup for Linux, UNIX and Windows	Affected >=12.1.0.0 <=2.1.0	Fixed in–

CPE configurations (1)

cpe:2.3:a:ibm:db2_merge_backup_for_linux_unix_and_windows:12.1.0.0:*:*:*:*:*:*:*

AI-suggested

Organizations should first verify if they are running IBM DB2 Merge Backup version 12.1.0.0 and plan to upgrade to a patched version once available. In the absence of an official patch, administrators should restrict local access to systems running the vulnerable DB2 version, enforcing strict user privilege controls and monitoring for unusual local activity. Employing memory protection mechanisms such as address space layout randomization (ASLR) and ensuring that backup processes run with the minimum necessary privileges can reduce exploitation likelihood. Additionally, implementing host-based intrusion detection systems (HIDS) to detect unauthorized memory access attempts and conducting regular audits of user permissions can help mitigate risk. Organizations should also consider encrypting backup data at rest and in transit to minimize the impact of any potential data leakage. Finally, maintaining an incident response plan that includes scenarios involving insider threats or local privilege abuse is advisable.

Description

IBM DB2 Merge Backup for Linux, UNIX and Windows 12.1.0.0 could allow an attacker to access sensitive information in memory due to the buffer not properly clearing resources.

Impact

This vulnerability can lead to unauthorized disclosure of sensitive information stored in memory buffers during the DB2 merge backup process. For organizations, this could mean exposure of confidential database contents or backup metadata to local attackers with limited privileges, potentially facilitating further attacks or data breaches. While it does not allow modification or disruption of services, the confidentiality breach could undermine compliance with data protection regulations and damage organizational reputation. The impact is particularly significant for enterprises relying on IBM DB2 12.1.0.0 for critical data backup operations, especially in environments where multiple users have local access or where privilege escalation is possible. Since the attack requires local access, remote exploitation is not feasible, but insider threats or compromised accounts could leverage this vulnerability. The absence of known exploits reduces immediate risk but does not eliminate the potential for future attacks.

CWE-226Sensitive Information in Resource Not Removed Before Reuse (opens in a new tab)
Base weakness
The product releases a resource such as memory or a file so that it can be made available for reuse, but it does not clear or "zeroize" the information contained in the resource before the product performs a critical state transition or makes the resource available for reuse by other entities.
Architecture and Design · Implementation
During critical state transitions, information not needed in the next state should be removed or overwritten with fixed patterns (such as all 0's) or random data, before the transition to the next state.
Architecture and Design · Implementation
When releasing, de-allocating, or deleting a resource, overwrite its data and relevant metadata with fixed patterns or random data. Be cautious about complex resource types whose underlying representation might be non-contiguous or change at a low level, such as how a file might be split into different chunks on a…
OWASP ASVS 4.0.3
V8.3.6 (opens in a new tab)
V8.3.2 (opens in a new tab)
Attack patterns
Retrieve Embedded Sensitive Data (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

CPE configurations (1)

Description

AI analysisMachine-generated, updated 26 Feb 2026, 23:11 UTC

WeaknessesCWE-226

Technical details

References

Community reviews

Related threats