# CVE-2026-3457: Stored XSS vulnerability in Sentinel ACC

> Stored XSS in Thales Sentinel LDK Runtime allows attackers to inject scripts, potentially leading to code execution or security bypass.

- **Severity:** High 7.0 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:N/SC:L/SI:H/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Mar 2026
- **Updated:** 3 Sep 2026
- **Also known as:** GHSA-p8p4-668f-3c4x

## What is CVE-2026-3457?

CVE-2026-3457 is a high-severity cross-site scripting vulnerability in Thalesgroup Sentinel LDK Runtime, published on 27 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Thales Sentinel LDK Runtime on Windows allows Stored XSS.

This issue affects Sentinel LDK Runtime: before 10.22.

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

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


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

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

## Is CVE-2026-3457 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-3457 is a high-severity cross-site scripting vulnerability in Thalesgroup Sentinel LDK Runtime, published on 27 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-3457 in the wild and no public exploit code.

Affected product: Thalesgroup Sentinel LDK Runtime. 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-3457/ (Markdown: https://insights.sbomify.com/CVE-2026-3457/index.md)
```

## Sources

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

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