Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-36425: CWE-256 in IBM Db2 for Linux, UNIX and Windows

0
Medium
VulnerabilityCVE-2025-36425cvecve-2025-36425cwe-256
Published: Tue Feb 17 2026 (02/17/2026, 17:13:03 UTC)
Source: CVE Database V5
Vendor/Project: IBM
Product: Db2 for Linux, UNIX and Windows

Description

IBM Db2 for Linux, UNIX and Windows (includes Db2 Connect Server) 11.5.0 through 11.5.9 and 12.1.0 through 12.1.3 could allow an authenticated user to obtain sensitive information under specific HADR configuration.

AI-Powered Analysis

AILast updated: 02/18/2026, 08:21:25 UTC

Technical Analysis

CVE-2025-36425 is a vulnerability identified in IBM Db2 for Linux, UNIX, and Windows, specifically affecting versions 11.5.0 through 11.5.9 and 12.1.0 through 12.1.3, including Db2 Connect Server. The issue arises under specific High Availability Disaster Recovery (HADR) configurations, where an authenticated user with low privileges can exploit improper credential or sensitive information management (classified under CWE-256: Plaintext Storage of a Password) to gain unauthorized access to sensitive data. The vulnerability is exploitable remotely over the network (Attack Vector: Network) but requires low-level privileges (Privileges Required: Low) and no user interaction. The attack complexity is high, indicating that exploitation requires specific conditions or knowledge about the HADR setup. The vulnerability impacts confidentiality but does not affect integrity or availability. No public exploits have been reported yet, and IBM has not released patches at the time of this report. The vulnerability was reserved in April 2025 and published in February 2026 with a CVSS v3.1 score of 5.3, reflecting a medium severity level. The root cause relates to insufficient protection of sensitive information within the HADR configuration, potentially exposing credentials or other critical data to authenticated users who should not have access. This could lead to unauthorized data disclosure, undermining the confidentiality of the database environment.

Potential Impact

For European organizations, this vulnerability poses a risk of sensitive data exposure within critical database environments, especially those leveraging IBM Db2 with HADR for business continuity and disaster recovery. Confidentiality breaches could lead to leakage of proprietary, financial, or personal data, potentially violating GDPR and other data protection regulations. Organizations in sectors such as finance, healthcare, government, and critical infrastructure that rely on IBM Db2 databases are particularly vulnerable. The requirement for authenticated access limits the attack surface to internal users or compromised credentials, but insider threats or lateral movement by attackers could exploit this flaw. The medium severity rating indicates a moderate risk, but the impact on confidentiality could be significant depending on the data exposed. Additionally, the complexity of exploitation suggests that only skilled attackers or those with detailed knowledge of the environment could leverage this vulnerability effectively. Nonetheless, the presence of this flaw in widely used enterprise database software necessitates prompt attention to prevent potential data breaches.

Mitigation Recommendations

1. Monitor IBM's official channels for patches addressing CVE-2025-36425 and apply them promptly once released. 2. Restrict database user privileges rigorously, ensuring that users have only the minimum necessary permissions, especially in environments using HADR. 3. Review and harden HADR configurations to minimize exposure of sensitive information, including auditing replication and failover settings. 4. Implement network segmentation and access controls to limit which authenticated users can connect to the database servers, reducing the risk of lateral movement. 5. Employ strong authentication mechanisms and monitor for unusual access patterns or privilege escalations within the database environment. 6. Conduct regular security audits and vulnerability assessments focusing on database configurations and user permissions. 7. Encrypt sensitive data at rest and in transit within the database and HADR channels to reduce the impact of potential data exposure. 8. Educate internal teams about the risks of insider threats and enforce strict credential management policies.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
ibm
Date Reserved
2025-04-15T21:17:02.754Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699575bb80d747be2053770c

Added to database: 2/18/2026, 8:18:03 AM

Last enriched: 2/18/2026, 8:21:25 AM

Last updated: 2/21/2026, 2:19:16 AM

Views: 18

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats