CVE-2025-36123 is a vulnerability classified under CWE-770 (Allocation of Resources Without Limits or Throttling) affecting IBM Db2 for Linux, UNIX, and Windows, including DB2 Connect Server, specifically versions 11.5.0 through 11.5.9 and 12.1.0 through 12.1.3. The flaw arises during the operation of copying large tables containing XML data, where the system improperly allocates resources without adequate limits or throttling mechanisms. This can lead to excessive consumption of system resources such as memory or CPU, resulting in a denial of service condition. The vulnerability requires local access but no privileges or user interaction, making it easier for an insider or compromised local account to trigger the issue. The CVSS v3.1 score is 6.2, indicating a medium severity level primarily due to the impact on availability (denial of service) without affecting confidentiality or integrity. No public exploits have been reported yet, and IBM has not published patches at the time of this report. The vulnerability could disrupt database availability, impacting applications and services dependent on Db2, particularly those processing large XML datasets. This resource exhaustion vulnerability highlights the need for proper resource management and input validation in database operations involving complex data types.

For European organizations, the primary impact of CVE-2025-36123 is the potential denial of service on critical database systems running IBM Db2, which could disrupt business operations, data processing, and service availability. Organizations relying on Db2 for large-scale XML data processing, such as financial institutions, healthcare providers, and government agencies, may experience outages or degraded performance. This could lead to operational delays, loss of productivity, and potential regulatory compliance issues if services become unavailable. Since the vulnerability requires local access, the risk is higher from insider threats or attackers who have already gained limited access to the network. The disruption of database services could also affect interconnected systems and applications, amplifying the impact. Given the widespread use of IBM Db2 in enterprise environments across Europe, the vulnerability poses a tangible risk to critical infrastructure and data-intensive sectors.

1. Monitor and restrict local user access to IBM Db2 servers to trusted personnel only, minimizing the risk of exploitation by unauthorized local users. 2. Implement resource usage monitoring and alerting on database servers to detect abnormal spikes in CPU, memory, or I/O that may indicate exploitation attempts. 3. Apply any IBM patches or updates addressing this vulnerability as soon as they become available. 4. Consider configuring database resource governor or workload management features to limit resource consumption during large data operations, especially involving XML data. 5. Conduct regular audits of database operations involving large XML tables to identify and optimize potentially resource-intensive queries or processes. 6. Employ network segmentation and access controls to limit lateral movement and reduce the likelihood of local access by untrusted users. 7. Prepare incident response plans to quickly address denial of service conditions affecting database availability.