IBM Cloud Pak System CVE-2026-4418

Exploitation requires the attacker to hold valid authenticated credentials to the IBM Cloud Pak System web interface (PR:L) and to place malicious HTML into a field that is stored or reflected back to other users. Successful impact additionally depends on a separate victim subsequently viewing the injected content (UI:R) - the payload does not execute without that victim interaction. These two factors (prior authentication plus required victim viewing) are the primary limits on real-world exploitability; only versions 2.3.6.0 and 2.3.6.1 are affected.

This is a medium-severity (CVSS 5.4) stored/reflected HTML injection (CWE-80) issue that should be treated as a routine patch-management item rather than an urgent priority. The CVSS vector (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N) tells a consistent story: network-reachable, low attack complexity, but it requires an already-authenticated attacker (PR:L) AND a victim to view the injected content (UI:R), with only Low confidentiality and integrity impact and no availability impact. The scope change (S:C) reflects that the payload executes in the victim's browser within the hosting site's security context, which is why CVSS still rates it above a pure low. No EPSS score was provided in the input, so exploitation probability cannot be quantified. There is no CISA KEV listing and no public POC identified, so there is no evidence of active or imminent exploitation. The main mitigating realities - attacker must hold valid credentials and a separate victim must view the malicious content - substantially lower real-world risk versus the raw score. No signals conflict; the description ('remotely authenticated attacker') and the CVSS PR:L are in agreement.

A low-privileged but authenticated user of the IBM Cloud Pak System web console submits input containing malicious HTML/script into a field that is later rendered to other users. When an administrator or another user views that content, the HTML executes in their browser within the site's security context, enabling session-context actions such as content spoofing or limited data theft. No public exploit code was identified at time of analysis.