CVE-2025-14688
Denial of Service in IBM Db2 due to Improper Input Handling
Publication date: 2026-04-30
Last updated on: 2026-05-01
Assigner: IBM Corporation
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| ibm | db2 | From 11.5.0 (inc) to 11.5.9 (inc) |
| ibm | db2 | From 11.5.0 (inc) to 11.5.9 (inc) |
| ibm | db2 | From 11.5.0 (inc) to 11.5.9 (inc) |
| ibm | db2 | From 12.1.0 (inc) to 12.1.3 (inc) |
| ibm | db2 | From 12.1.0 (inc) to 12.1.3 (inc) |
| ibm | db2 | From 12.1.0 (inc) to 12.1.3 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-1284 | The product receives input that is expected to specify a quantity (such as size or length), but it does not validate or incorrectly validates that the quantity has the required properties. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify how this vulnerability impacts compliance with common standards and regulations such as GDPR or HIPAA.
Can you explain this vulnerability to me?
This vulnerability affects IBM Db2 versions 11.5.0 through 11.5.9 and 12.1.0 through 12.1.3 on Linux, UNIX, and Windows platforms, including Db2 Connect Server. It allows an authenticated user to cause a denial of service by exploiting improper neutralization of special elements in data query logic when certain configurations are present.
How can this vulnerability impact me? :
The vulnerability can lead to a denial of service condition, meaning that an authenticated user could disrupt the normal operation of the IBM Db2 database server, potentially causing it to become unavailable or unresponsive.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability occurs when specific configuration variables are set in IBM Db2. To detect if your system is vulnerable, you should check the values of the following registry variables:
- DB2_WORKLOAD is set to ANALYTICS or intra_parallel is set to YES
- DB2_EXTENDED_OPTIMIZATION is set to NLJN_OFLOW
You can use the following command to check the value of DB2_EXTENDED_OPTIMIZATION:
- db2set -all | grep DB2_EXTENDED_OPTIMIZATION
Similarly, check the other configuration variables using db2set or your system's configuration tools to confirm if the vulnerable settings are present.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability immediately, you can remove the problematic registry variable that triggers the issue.
- Execute the command: db2set -im DB2_EXTENDED_OPTIMIZATION= to remove the NLJN_OFLOW setting.
Additionally, IBM provides interim fixes and special builds for affected versions. Applying these fixes is recommended for a permanent resolution:
- For version 11.5.9, apply the special build (mod pack APAR DT458000).
- For version 12.1.x, upgrade to version 12.1.4 or later where the fix is included.
Avoid disclosing detailed exploitation steps and ensure that only authenticated users have access to the system to reduce risk.