Multiple Vulnerabilities in IBM Cloud Pak System
IBM Cloud Pak System is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.
- Published
- Feb 4, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 21th percentile
- CWE
- CWE-209
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · ibm
- 5.3
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| ibm | cloud pak system | cpe:2.3:a:ibm:cloud_pak_system |
| ibm | os image for red hat linux systems | cpe:2.3:a:ibm:os_image_for_red_hat_linux_systems |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- ibm cloud pak system2.3.4.0
- ibm cloud pak system2.3.4.1
- ibm cloud pak system2.3.5.0
- ibm cloud pak system2.3.6.0
- ibm os image for red hat linux systems4.0.4.0
- ibm os image for red hat linux systems4.0.5.0
- ibm os image for red hat linux systems4.0.6.0
- ibm os image for red hat linux systems4.0.7.0
- ibm os image for red hat linux systems5.0.0.0
- ibm os image for red hat linux systems5.0.1.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (ibm). Independent of NVD's CPE analysis and usually ahead of it.
IBM Cloud Pak System
- 2.3.4.0, 2.3.4.1, 2.3.4.1 Interim Fix 001, 2.3.5.0, 2.3.6.0affected
IBM OS Image for Red Hat Linux Systems
- 4.0.4.0, 4.0.5.0, 4.0.6.0, 4.0.7.0, 5.0.0.0, 5.0.1.0affected
Same product
ibm: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-4521Platform System Manager in IBM Cloud Pak System 2.3 is potentially vulnerable to CVS Injection.40Plan
- CVE-2019-4130IBM Cloud Pak System 2.3 and 2.3.0.1 could allow a remote attacker to upload arbitrary files, which could allow the attacker to execute arbi36Monitor
- CVE-2020-4917IBM Cloud Pak System 2.3 is vulnerable to cross-site request forgery which could allow an attacker to execute malicious and unauthorized act35Monitor
- CVE-2026-13463Due to use of IBM Storage Protect, IBM Cloud Pak System is affected by vulnerability []30Monitor
- CVE-2023-38010Multiple Vulnerabilities in IBM Cloud Pak System30Monitor
- CVE-2023-38272IBM Cloud Pak System information disclosure30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2023-380100 days apartMultiple Vulnerabilities in IBM Cloud Pak System30Monitor
- CVE-2023-38713375 days apartIBM Cloud Pak System information disclosure30Monitor
- CVE-2023-38714375 days apartIBM Cloud Pak System information disclosure30Monitor
- CVE-2023-38716375 days apartIBM Cloud Pak System information disclosure30Monitor
- CVE-2023-382810 days apartMultiple Vulnerabilities in IBM Cloud Pak System21Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-209 · Generation of Error Message Containing Sensitive InformationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.