IBM Engineering AI Hub CVE-2026-15069

Exploitation requires that a victim user interact with attacker-controlled content rendered by the IBM Engineering AI Hub web interface - specifically, that the victim's browser loads and renders a page containing the injected script payload (UI:R per CVSS vector). No special server-side configuration beyond a default deployment of versions 1.0.0, 1.1.0, or 1.2.0 is required. The PR:N CVSS metric indicates the attacker does not need to authenticate to the IBM Engineering AI Hub application to deliver the payload. Exploitation is constrained to the victim's browser session context (S:U, scope unchanged), meaning the attacker cannot directly pivot to the underlying server operating system or adjacent systems through this flaw alone. Limiting factors include: the attacker must be able to reach the Engineering AI Hub web interface over the network, and a human victim must be socially engineered or otherwise induced to interact with the malicious content.

The CVSS base score of 5.4 (Medium) reflects a network-accessible, low-complexity flaw that requires no attacker authentication (PR:N) but depends on victim interaction (UI:R), with limited confidentiality and integrity impact (C:L/I:L) and no availability impact. EPSS data was not provided in available intelligence, so a quantified exploitation probability cannot be stated. The vulnerability is not listed in the CISA KEV catalog, and no proof-of-concept code has been identified, indicating no confirmed or widespread exploitation at time of analysis. Real-world risk is moderate: successful exploitation could enable session hijacking, credential theft, or unauthorized in-application actions within the victim's browser context, but the UI:R prerequisite reduces the likelihood of automated or mass exploitation. IBM Engineering AI Hub serves a narrow enterprise engineering audience, limiting the aggregate attack surface compared to broadly deployed web platforms. This represents a genuine but non-urgent patching priority for organizations running the affected versions.

An attacker identifies a publicly or internally accessible IBM Engineering AI Hub instance running a vulnerable version and crafts a URL or form submission embedding a JavaScript payload in an unsanitized input field. The attacker distributes the crafted link via phishing email to an engineer who uses the platform, and upon clicking, the victim's browser renders the malicious script within the Engineering AI Hub web context. The attacker's script exfiltrates the victim's session cookie or authentication token to an attacker-controlled server, enabling session hijacking and unauthorized access to the engineering platform.