dbcve.org
Cloud Pak For Data System CyclopsApplication · Ibm

CVE-2025-36220

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-26
Fix available
A fix is available. Upgrade to 11.3.0.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
IBM Cloud Pak for Data System - Cyclops 11.3.0.2 through Interim Fix 002 IBM Cloud Pak for Data System is vulnerable to SQL injection. A remote attacker could send specially crafted SQL statements, which could allow the attacker to view, add, modify, or delete information in the back-end database.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in IBM Cloud Pak for Data System Cyclops component (versions 11.3.0.2 through Interim Fix 002) allows remote unauthenticated attackers to execute arbitrary SQL commands against the back-end database, potentially enabling data exfiltration, modification, or deletion.

MitigationApply IBM's interim fix for this vulnerability. Until patched, consider network segmentation and web application firewall rules to mitigate exploitation risk.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Cloud Pak For Data System CyclopsApplication
Affected:< 11.3.0.2= 11.3.0.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Cyclops component presence
    Locate the IBM Cloud Pak for Data System installation and confirm the Cyclops component is deployed. This may be visible in the system inventory, deployment manifests, or product documentation.
    Affected if Cyclops component is present in the environment
  2. Determine Cyclops component version
    Query the installed version of the Cyclops component. This can typically be obtained via the IBM Cloud Pak for Data System management interface, command-line tools, or component-specific metadata files.
    Affected if Version is 11.3.0.2 or lower
  3. Check Interim Fix level
    Determine which Interim Fix (IFix) level is applied to the Cyclops component. Check the fix package or patch inventory for the installed Cyclops component.
    Affected if Interim Fix 003 or later is NOT installed (meaning IFix 002 or earlier / no fix is applied)
  4. Verify Cyclops network exposure
    Confirm whether the Cyclops service is network-accessible from untrusted networks. This vulnerability allows remote unauthenticated SQL injection, so external accessibility is required for exploitation.
    Affected if Cyclops component is exposed to untrusted network segments or the internet

The environment is affected if IBM Cloud Pak for Data System with the Cyclops component is installed, the Cyclops version is 11.3.0.2 or lower, and Interim Fix 003 has not been applied, particularly if the service is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 11.3.0.2 or later
Fixed in 11.3.0.2
Interim mitigation

Apply IBM's interim fix for this vulnerability. Until patched, consider network segmentation and web application firewall rules to mitigate exploitation risk.

Recommended fix Moderate confidence

IBM Cloud Pak for Data System Cyclops 11.3.0.3 or later (or latest available Interim Fix beyond IF002)

  1. 1. Identify the current installed version of IBM Cloud Pak for Data System Cyclops
  2. 2. Contact IBM support or visit the official IBM support portal to obtain the latest available fix/patch for this vulnerability
  3. 3. Schedule a maintenance window for the upgrade process
  4. 4. Back up all critical data and configurations
  5. 5. Download the patched version (11.3.0.3 or later, or a later Interim Fix beyond IF002)
  6. 6. Apply the upgrade following IBM's documented upgrade procedures
  7. 7. Verify the installation and test that the SQL injection vulnerability is resolved
  8. 8. Validate that all critical business functions operate correctly post-upgrade
Caveat Review IBM's release notes for any compatibility changes or deprecations between 11.3.0.2 and the target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cloud Pak For Data System Cyclops Scoped from the published advisory
  • Consultation8.0 h
  • Implementation32.0 h
  • Testing16.0 h
  • Review / QA8.0 h
64.0 hours of engineering $11,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $17,920.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-36220 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-36220 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data