CVE-2025-36220

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 76% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
24%
KEV
Not listed

Published

May 26, 2026

Last Modified

July 24, 2026

Advisory Details (1)

Auto-updated Sep 11, 2026
No patch confirmed yet.
generic

Security Bulletin: Vulnerabilities exists in IBM Cloud Pak for Data System (CPDS 1.0) - Cyclops.

https://www.ibm.com/support/pages/node/7273923

Vendor Advisories for CVE-2025-36220(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 39× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 258 total refreshes for this CVE.

  1. 2026-09-16 05:14 UTCEPSS rescore
  2. 2026-09-13 16:46 UTCEPSS rescore
  3. 2026-09-12 15:00 UTCEPSS rescore
  4. 2026-09-11 14:52 UTCEPSS rescore
  5. 2026-09-11 09:35 UTCEPSS rescore
  6. 2026-09-10 09:33 UTCEPSS rescore
  7. 2026-09-08 21:59 UTCEPSS rescore
  8. 2026-09-07 16:00 UTCEPSS rescore
  9. 2026-09-06 13:46 UTCEPSS rescore
  10. 2026-09-04 05:05 UTCEPSS rescore
  11. 2026-09-02 14:11 UTCEPSS rescore
  12. 2026-09-01 13:53 UTCEPSS rescore
  13. 2026-09-01 04:38 UTCEPSS rescore
  14. 2026-08-30 19:16 UTCEPSS rescore
  15. 2026-08-30 01:21 UTCEPSS rescore
  16. 2026-08-28 21:40 UTCEPSS rescore
  17. 2026-08-27 14:24 UTCEPSS rescore
  18. 2026-08-26 14:45 UTCEPSS rescore
  19. 2026-08-25 13:48 UTCEPSS rescore
  20. 2026-08-24 00:18 UTCGHSA enrichment
  21. 2026-08-23 19:52 UTCGHSA enrichment
  22. 2026-08-23 15:59 UTCEG score recompute
  23. 2026-08-23 15:59 UTCGHSA enrichment
  24. 2026-08-23 00:18 UTCEPSS rescore
  25. 2026-08-22 01:17 UTCEG score recompute
Show 75 more
  1. 2026-08-22 01:17 UTCGHSA enrichment
  2. 2026-08-21 23:48 UTCEPSS rescore
  3. 2026-08-21 21:23 UTCEG score recompute
  4. 2026-08-21 21:23 UTCGHSA enrichment
  5. 2026-08-20 22:54 UTCEPSS rescore
  6. 2026-08-20 22:42 UTCGHSA enrichment
  7. 2026-08-20 18:04 UTCEG score recompute
  8. 2026-08-20 18:04 UTCGHSA enrichment
  9. 2026-08-19 17:03 UTCEPSS rescore
  10. 2026-08-19 17:03 UTCEPSS rescore
  11. 2026-08-18 13:47 UTCEPSS rescore
  12. 2026-08-17 13:46 UTCEPSS rescore
  13. 2026-08-17 13:41 UTCGHSA enrichment
  14. 2026-08-17 09:33 UTCGHSA enrichment
  15. 2026-08-16 16:32 UTCEG score recompute
  16. 2026-08-16 16:32 UTCGHSA enrichment
  17. 2026-08-16 14:55 UTCEPSS rescore
  18. 2026-08-16 10:51 UTCGHSA enrichment
  19. 2026-08-16 06:58 UTCGHSA enrichment
  20. 2026-08-16 03:06 UTCEG score recompute
  21. 2026-08-16 03:06 UTCGHSA enrichment
  22. 2026-08-16 02:13 UTCEPSS rescore
  23. 2026-08-15 01:44 UTCEG score recompute
  24. 2026-08-15 01:44 UTCGHSA enrichment
  25. 2026-08-15 01:29 UTCEPSS rescore
  26. 2026-08-14 21:52 UTCGHSA enrichment
  27. 2026-08-14 17:59 UTCGHSA enrichment
  28. 2026-08-14 13:21 UTCGHSA enrichment
  29. 2026-08-14 09:28 UTCGHSA enrichment
  30. 2026-08-14 05:35 UTCGHSA enrichment
  31. 2026-08-14 01:42 UTCEG score recompute
  32. 2026-08-14 01:42 UTCGHSA enrichment
  33. 2026-08-13 21:59 UTCEPSS rescore
  34. 2026-08-13 09:47 UTCGHSA enrichment
  35. 2026-08-13 05:54 UTCGHSA enrichment
  36. 2026-08-13 01:37 UTCGHSA enrichment
  37. 2026-08-12 21:44 UTCGHSA enrichment
  38. 2026-08-12 17:51 UTCGHSA enrichment
  39. 2026-08-12 13:58 UTCEG score recompute
  40. 2026-08-12 13:58 UTCGHSA enrichment
  41. 2026-08-12 13:50 UTCEPSS rescore
  42. 2026-08-12 09:41 UTCGHSA enrichment
  43. 2026-08-12 02:20 UTCGHSA enrichment
  44. 2026-08-11 22:26 UTCGHSA enrichment
  45. 2026-08-11 18:34 UTCEG score recompute
  46. 2026-08-11 18:34 UTCGHSA enrichment
  47. 2026-08-11 13:41 UTCGHSA enrichment
  48. 2026-08-11 08:09 UTCGHSA enrichment
  49. 2026-08-11 04:14 UTCGHSA enrichment
  50. 2026-08-11 00:22 UTCEG score recompute
  51. 2026-08-11 00:22 UTCGHSA enrichment
  52. 2026-08-10 10:33 UTCGHSA enrichment
  53. 2026-08-10 06:39 UTCGHSA enrichment
  54. 2026-08-10 02:46 UTCGHSA enrichment
  55. 2026-08-09 22:54 UTCGHSA enrichment
  56. 2026-08-09 19:00 UTCGHSA enrichment
  57. 2026-08-09 15:08 UTCEG score recompute
  58. 2026-08-09 15:08 UTCGHSA enrichment
  59. 2026-08-09 13:46 UTCEPSS rescore
  60. 2026-08-09 11:15 UTCGHSA enrichment
  61. 2026-08-09 07:22 UTCGHSA enrichment
  62. 2026-08-09 03:29 UTCGHSA enrichment
  63. 2026-08-08 23:36 UTCGHSA enrichment
  64. 2026-08-08 11:42 UTCGHSA enrichment
  65. 2026-08-08 07:47 UTCGHSA enrichment
  66. 2026-08-08 03:54 UTCGHSA enrichment
  67. 2026-08-08 00:01 UTCGHSA enrichment
  68. 2026-08-07 20:08 UTCEG score recompute
  69. 2026-08-07 20:08 UTCGHSA enrichment
  70. 2026-08-07 16:26 UTCEPSS rescore
  71. 2026-08-07 16:15 UTCGHSA enrichment
  72. 2026-08-07 12:22 UTCGHSA enrichment
  73. 2026-08-07 08:29 UTCGHSA enrichment
  74. 2026-08-07 04:36 UTCGHSA enrichment
  75. 2026-08-07 00:43 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2025-36220?
CVE-2025-36220 is a critical vulnerability published on May 26, 2026. 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.
When was CVE-2025-36220 disclosed?
CVE-2025-36220 was first published in the National Vulnerability Database on May 26, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-36220 actively exploited?
CVE-2025-36220 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 76.3% of all scored CVEs.
What is the CVSS score of CVE-2025-36220?
CVE-2025-36220 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2025-36220?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-36220, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-36220

Explore →

Is Your Infrastructure Affected by CVE-2025-36220?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.