# CVE-2026-76975: Cross-Site Scripting (XSS) vulnerability in SAPUI5 (Support Assistant Overlay)

> An attacker can execute arbitrary scripts in a victim's browser via a malicious link, compromising confidentiality and integrity of user data.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-63m2-wc55-cxrv

## What is CVE-2026-76975?

CVE-2026-76975 is a medium-severity cross-site scripting vulnerability in SAP_SE SAPUI5 (Support Assistant Overlay), published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Due to a DOM-Based Cross-Site Scripting (XSS) vulnerability, an unauthenticated attacker could generate a malicious link and make it publicly accessible. If an authenticated user accesses this link, client-side code reads the attacker-controlled input and writes it into the DOM without proper sanitization, causing attacker-supplied script to execute in the victim�s browser context. This could allow the attacker to access or modify information within the victim�s browser scope, impacting confidentiality and integrity, while availability remains unaffected.

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

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


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

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

## Is CVE-2026-76975 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76975 is a medium-severity cross-site scripting vulnerability in SAP_SE SAPUI5 (Support Assistant Overlay), published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-76975 in the wild and no public exploit code.

Affected product: SAP_SE SAPUI5 (Support Assistant Overlay). 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-76975/ (Markdown: https://insights.sbomify.com/CVE-2026-76975/index.md)
```

## Sources

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

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