Stored XSS vulnerability in Sentinel ACC

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps Thales/Sentinel LDK Runtime (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for Thales/Sentinel LDK Runtime.
2. 2Review the reported fix. Update Thales/Sentinel LDK Runtime to 10.22 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

1. Published upstream

   Mar 27, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Aug 26, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Aug 26, 2026

Sources and claim methodology

• Source referencesupportportal.thalesgroup.com

Related CVEs

• Winter: Stored XSS through Brand Settings custom stylesAlso CWE-79
• Winter: Stored XSS through Editor Settings custom stylesAlso CWE-79
• SunEditor: DOM XSS in SunEditor Embed Plugin via External Script Element After Iframe EmbedAlso CWE-79
• FiftyOne before 1.21.0 Stored Cross-Site Scripting via Unescaped Field DescriptionAlso CWE-79
• Winter: Authenticated backend users can bypass Users controller permission checksSame generic ecosystem
• Nagios Core CSRF via cmd.cgiSame generic ecosystem