# CVE-2026-41200: STIG Manager has reflected XSS vulnerability in the Web App

> Attackers can execute arbitrary JavaScript via reflected XSS in OIDC error handling, potentially reading and modifying data in active sessions.

- **Severity:** High 8.5 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA: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:** 23 Apr 2026
- **Updated:** 23 Apr 2026
- **Also known as:** GHSA-wg33-j3rv-jq72

## What is CVE-2026-41200?

CVE-2026-41200 is a high-severity cross-site scripting vulnerability in NUWCDIVNPT stig-manager, published on 23 Apr 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

STIG Manager is an API and web client for managing  Security Technical Implementation Guides (STIG) assessments of Information Systems. Versions 1.5.10 through 1.6.7 have a reflected Cross-Site Scripting (XSS) vulnerability in the OIDC authentication error handling code in `src/init.js` and `public/reauth.html`. During the OIDC redirect flow, the `error` and `error_description` query parameters returned by the OIDC provider are written directly to the DOM via `innerHTML` without HTML escaping. An attacker who can craft a malicious redirect URL and convince a user to follow it can execute arbitrary JavaScript in the application's origin context. The vulnerability is most severe when the targeted user has an active STIG Manager session running in another browser tab — injected code executes in the same origin and can communicate with the SharedWorker managing the active access token, enabling authenticated API requests on behalf of the victim including reading and modifying collection data. The vulnerability is patched in version 1.6.8. There is no workaround short of upgrading. Deployments behind a web application firewall that filters reflected XSS payloads in query parameters may have partial mitigation, but this is not a substitute for patching.

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

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


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

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

## Is CVE-2026-41200 being exploited?

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

Public exploit code:

- https://github.com/Hunt-Benito/cve-2026-41200-stig-manager-oidc-reflected-xss (github_poc): https://github.com/Hunt-Benito/cve-2026-41200-stig-manager-oidc-reflected-xss

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41200 is a high-severity cross-site scripting vulnerability in NUWCDIVNPT stig-manager, published on 23 Apr 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-41200 in the wild and no public exploit code.

Affected product: NUWCDIVNPT stig-manager. 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-41200/ (Markdown: https://insights.sbomify.com/CVE-2026-41200/index.md)
```

## Sources

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

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