External risk intelligence

IBM Cloud Pak for Data System Cyclops SQL Injection Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2025-36220

IBM Cloud Pak for Data System is a platform for data and AI workloads. While it contains web-based components that may be reachable from the network, it is typically deployed within internal enterprise data centers or private cloud environments rather than directly exposed to the public internet as a primary design feature.

SQL Injection

Ibm Cloud Pak For Data System Cyclops

before 11.3.0.211.3.0.2

Halo Surface Signal: 3 out of 5 — possibly public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

IBM Cloud Pak for Data System is affected by a critical vulnerability that allows a remote attacker to manipulate sensitive data. This SQL injection flaw could permit unauthorized viewing, modification, or deletion of information within the system's backend database. The main concern is confirming relevance and exposure due to the typical internal deployment of this platform.

  • Attackers can alter sensitive data through SQL injection.
  • Critical vulnerability affects data integrity and confidentiality.
  • Confirm if this platform is deployed in your environment.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by sending specially crafted SQL statements over the network to the affected IBM Cloud Pak for Data System. This could allow them to interact with the back-end database, potentially leading to unauthorized data access, modification, or deletion.

  • No authentication or user interaction needed.
  • Specially crafted SQL statements trigger vulnerability.
  • Allows attacker to view, add, modify, or delete data.

Live Threat

Current exploitation, exposure, and threat context

A remote attacker could exploit this vulnerability by sending specially crafted SQL statements. When successful, this could allow the attacker to view, add, modify, or delete information within the back-end database of IBM Cloud Pak for Data System.

  • Database information could be at risk.
  • Malicious SQL statements could be sent over the network.
  • Unauthorized data access or modification may occur.

Operational Fix

Recommended remediation, mitigation, and detection steps

Real-world ownership for this SQL injection vulnerability in IBM Cloud Pak for Data System likely falls to platform or infrastructure teams responsible for the Cloud Pak deployment, as well as application owners who utilize its data capabilities. The initial practical move involves identifying all instances of the affected technology, confirming network reachability and business criticality, and then identifying the accountable owner for each instance to plan remediation based on risk.

  • Platform and application owners are responsible.
  • Verify network exposure and business criticality.
  • Plan remediation by risk and criticality.

Supplementary metadata

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is the IBM Cloud Pak for Data System - Cyclops?

It is an integrated platform used by organizations to manage data, analytics, and AI workloads. Think of it as a comprehensive infrastructure solution that bundles hardware and software to help businesses organize, analyze, and govern their information at scale. By centralizing these complex data tasks, it allows teams to build and deploy models or applications without managing every individual software layer separately.

What does SQL injection mean for CVE-2025-36220?

This vulnerability falls under the CWE-89 weakness class, which happens when an application fails to properly sanitize user-supplied data before including it in a database query. In this case, an attacker can input specially crafted SQL code instead of expected data. Because the system mistakenly treats this input as a valid command, it executes the attacker's instructions, granting them the ability to read, change, or erase information stored in the backend database.

How can an attacker trigger this vulnerability?

An attacker triggers this flaw by sending a malicious SQL statement over the network to the affected system. Importantly, the vulnerability does not require the attacker to have a pre-existing account or login credentials, nor does it require a legitimate user to click or interact with anything for the attack to succeed. Simply having network access to the target component is sufficient to attempt the injection.

Do I need to worry about this if my system is internal?

While Halo Surface Signal notes this platform is typically deployed within private data centers or internal clouds, you should still evaluate your specific setup. If your internal network allows traffic from untrusted segments or remote access points, the system could still be reachable by an attacker. Prioritize identifying where these instances reside on your network to determine if they are truly isolated from unauthorized access.

What are the first steps to address this issue?

Start by auditing your infrastructure to create a complete inventory of all deployed IBM Cloud Pak for Data System instances. Once you have a list, work with your platform and application owners to assess the business criticality and network accessibility of each instance. Use this information to prioritize which systems need immediate attention and coordinate with your internal technical teams to follow the official guidance provided by IBM.

References

Sources and related resources

Primary sources: NVD, CVE.org.

NVDPublished Modified