# CVE-2026-3295: IBM Cloud Pak System Cross-Site Scripting

> An authenticated attacker can inject malicious JavaScript into IBM Cloud Pak System, leading to stored XSS and potential session hijacking or code execution.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-g698-cvpw-9x59

## What is CVE-2026-3295?

CVE-2026-3295 is a high-severity cross-site scripting vulnerability in IBM Cloud Pak System, published on 19 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM Cloud Pak System 2.3.6.0, and 2.3.6.1 is vulnerable to cross site scripting. The web app user‑supplied input is not properly sanitized or HTML‑encoded before being stored and rendered. An authenticated attacker could exploit this vulnerability by entering specially crafted payloads containing malicious JavaScript which are saved within the app and later executed automatically when user views affected pages, resulting in Stored Cross‑Site Scripting (Stored XSS).

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-3295?


## How do I fix CVE-2026-3295?

No fix has been published for CVE-2026-3295 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-3295 being exploited?

There is no known exploitation of CVE-2026-3295 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-3295 and fix it if it is affected.

What it is: CVE-2026-3295 is a high-severity cross-site scripting vulnerability in IBM Cloud Pak System, published on 19 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-3295 in the wild and no public exploit code.

Affected product: IBM Cloud Pak System. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-3295/ (Markdown: https://insights.sbomify.com/CVE-2026-3295/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-3295
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-3295
- OSV: https://osv.dev/vulnerability/CVE-2026-3295

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-3295/
Summaries are generated and may contain mistakes; the official description above is the record.