CVE-2025-13108
Information Disclosure via Improper Memory Clearing in IBM DB2 Backup
Publication date: 2026-02-17
Last updated on: 2026-02-26
Assigner: IBM Corporation
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| ibm | db2_merge_backup | 12.1.0.0 |
| ibm | db2_merge_backup | 12.1.0.0 |
| ibm | db2_merge_backup | 12.1.0.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-226 | 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-13108 affects IBM Db2 Merge Backup for Linux, UNIX, and Windows version 12.1.0.0. The vulnerability occurs because the software does not properly clear buffer resources after use, which allows sensitive information to remain in memory.
An attacker with local access and low privileges can exploit this flaw to access sensitive information stored in memory that should have been cleared.
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized disclosure of sensitive information because an attacker with local access and low privileges can read residual data left in memory buffers.
The impact is primarily on confidentiality, with no effect on data integrity or system availability.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, users should download and install the IBM Interim Fix 12.1.0.0.1 for IBM Db2 Merge Backup version 12.1.0.0.
No workarounds or alternative mitigations are provided, so applying the official fix is the recommended immediate step.