# CVE-2026-66771: Cross Site Scripting (XSS) vulnerability in SAPUI5

> An attacker with content adaptation privileges can inject malicious scripts into SAPUI5 applications, allowing them to steal session data and perform unauthorized actions on behalf of other users.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-v37p-2wmc-8vqg

## What is CVE-2026-66771?

CVE-2026-66771 is a medium-severity cross-site scripting vulnerability in SAP_SE SAPUI5, published on 11 Aug 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

SAPUI5 allows a key user with content adaptation privileges to inject malicious script content into persisted application changes. When another user subsequently opens the adapted application, the injected script executes in the victim's browser session. Successful exploitation could allow the attacker to access sensitive session data and perform unauthorized actions on behalf of the victim, resulting in a high impact on confidentiality and integrity. There is no impact on availability.

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

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


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

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

## Is CVE-2026-66771 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-66771 is a medium-severity cross-site scripting vulnerability in SAP_SE SAPUI5, published on 11 Aug 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-66771 in the wild and no public exploit code.

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

## Sources

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

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