CVE-2025-0165 is a high severity (CVSS 7.6) SQL injection in IBM watsonx Orchestrate Cartridge for IBM Cloud Pak for Data, versions 4.8.4, 4.8.5 and 5.0.0 through 5.2.0. IBM recommends upgrading to watsonx Orchestrate Cartridge 5.2.0.1, and its bulletin lists no workaround or mitigation, so plan the upgrade soon.
What's affected
IBM's security bulletin lists IBM watsonx Orchestrate Cartridge for IBM Cloud Pak for Data in versions 4.8.4 through 4.8.5 and 5.0.0 through 5.2. It describes the problem as a blind SQL injection. A remote attacker could send specially crafted SQL statements, which could allow them to view, add, modify or delete information in the back end database.
The CVSS vector in the record requires low privileges, so an attacker needs an account on the system, but not a high one. Confidentiality impact is high and the integrity and availability impacts are low.
IBM recommends upgrading to IBM watsonx Orchestrate Cartridge 5.2.0.1 and says there are no workarounds or mitigations. The bulletin was first published on 29 August 2025.
How to check if you're exposed
Check the installed cartridge version through your Cloud Pak for Data administration.
- Sign in to the Cloud Pak for Data web client as an administrator and open the services or instances view to see the version of the watsonx Orchestrate service.
- If you manage the platform with the command line, use your normal Cloud Pak for Data tooling to list installed services and versions, and compare with the affected list.
- Review which accounts have access to the watsonx Orchestrate service, since the attack needs a login.
- Look at database and application logs for unusual queries or error bursts from the service.
If your version is 4.8.4, 4.8.5 or anything from 5.0.0 through 5.2, plan the upgrade.
What to do now
- Identify all Cloud Pak for Data deployments that include the watsonx Orchestrate cartridge.
- Upgrade to watsonx Orchestrate Cartridge 5.2.0.1, following IBM's on premises installation instructions.
- Review which users hold accounts with access to the service and remove stale ones.
- Review database and application logs for unusual queries.
- If you run a 4.8.x version, check IBM's installation instructions for how to reach 5.2.0.1.
- Record the new version in your inventory.
Why it matters
SQL injection is the case where text that a user supplies changes the meaning of a database query. The record calls it a blind injection, which means the attacker cannot see query results directly, and has to infer data from behavior, for example differences in responses. That is slower but entirely workable with automation.
The class is neutralization of special elements in an SQL command. The fix is to use parameterized queries so that input never changes the shape of the statement. The need for a login lowers the risk compared with an open endpoint, but stolen or shared credentials are common, so the upgrade is still worth doing promptly.
The weakness class is CWE-89: SQL Injection. The CVSS vector in the record is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L, which scores 7.6. This CVE is not listed in the CISA Known Exploited Vulnerabilities catalog at the time of writing.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Which version fixes it?
IBM recommends upgrading to watsonx Orchestrate Cartridge 5.2.0.1.
Is there a workaround?
IBM lists no workarounds or mitigations.
Sources
Last reviewed: 19 October 2026.
