# CVE-2026-71802: Cross-site scripting in n/a

> Stored XSS in REBUILD announcement preview allows attackers to execute arbitrary JavaScript in user browsers via malicious content.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-8wq2-j7c6-cq65

## What is CVE-2026-71802?

CVE-2026-71802 is a medium-severity cross-site scripting vulnerability in n/a, published on 9 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A stored Cross-Site Scripting (XSS) vulnerability exists in the announcement preview component of REBUILD 4.4.3. Although the announcement content undergoes HTML escaping on the server side, the client-side preview code reverses the escaped entities using jQuery's `html().text()` method and subsequently injects the result into the DOM. An administrator or attacker capable of controlling the announcement content can exploit this vulnerability to execute arbitrary JavaScript code in the browsers of users viewing the affected pages "which may include the dashboard, activity feed, or login page, depending on the announcement's visibility settings.

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

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


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

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

## Is CVE-2026-71802 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-71802 is a medium-severity cross-site scripting vulnerability in n/a, published on 9 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-71802 in the wild and no public exploit code.

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

## Sources

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

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