PatchTheCVEdb2 merge backup vulnerabilities and fixes
Recent CVEs affecting db2 merge backup, with upgrade or downgrade steps. 3 tracked.
Also searched as: db2mergebackup.
db2 merge backup has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2026-02-17. Highest priority: CVE-2025-33130 (score 33/100).
- CVE-2025-33130 MEDIUM 6.5 DOWNGRADE DOWNGRADE IBM DB2 Merge Backup for Linux, UNIX and Windows 12.1.0.0 could allow an authenticated user to cause the progr
- CVE-2025-33124 MEDIUM 6.5 DOWNGRADE IBM DB2 Merge Backup for Linux, UNIX and Windows 12.1.0.0 could allow an authenticated user to cause the progr
- CVE-2025-13108 MEDIUM 5.5 DOWNGRADE DOWNGRADE IBM DB2 Merge Backup for Linux, UNIX and Windows 12.1.0.0 could allow an attacker to access sensitive informat
FAQ
How do I fix db2 merge backup vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is db2 merge backup being exploited right now?
None of the tracked db2 merge backup CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which db2 merge backup CVE should I patch first?
CVE-2025-33130 currently ranks highest (33/100): IBM DB2 Merge Backup for Linux, UNIX and Windows 12.1.0.0 could allow an authenticated user to cause the progr.