dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-3457

HIGH · 7.0 CVSS v4.0 Published 2026-03-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
75/100
Remediation priority · High
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Stored XSS vulnerability in Thales Sentinel LDK Runtime's web interface allows attackers to inject malicious scripts that persist on the server and execute when other users access affected web pages. The vulnerability stems from improper input neutralization during web page generation.

MitigationUpgrade Sentinel LDK Runtime to version 10.22 or later to obtain the vendor patch. If immediate upgrade is not feasible, restrict web interface access to trusted users and implement input validation as a temporary compensating control.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Sentinel LDK Runtime installation
    On Windows, check registry key HKEY_LOCAL_MACHINE\SOFTWARE\Thales\Sentinel or look in common installation directories such as C:\Program Files\Thales\Sentinel LDK Runtime. On Linux, check /opt/sentinel_ldk_runtime or similar directories.
    Affected if Sentinel LDK Runtime software is not found on the system
  2. Determine installed version
    Locate the version information in the registry (check Version value under the Thales\Sentinel key), in an About or Readme file within the installation directory, or by running the haspdinst -v command if available.
    Affected if The installed version cannot be determined or is lower than 10.22
  3. Verify web interface is enabled
    Check if the Sentinel LDK web service is running. On Windows, look for a Sentinel LDK Web Server or similar service in Services.msc. On Linux, check for running processes like 'sentinel_ldk_web' or 'hasplmd' with web interface ports (typically 1947 or 8080).
    Affected if The web interface service is actively running and accessible on the network or localhost

A user is affected if their Sentinel LDK Runtime version is below 10.22 AND the web interface feature is enabled and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Sentinel LDK Runtime to version 10.22 or later to obtain the vendor patch. If immediate upgrade is not feasible, restrict web interface access to trusted users and implement input validation as a temporary compensating control.

Recommended fix Moderate confidence

Sentinel LDK Runtime version 10.22

  1. 1. Identify the current version of Sentinel LDK Runtime installed on the Windows system (check via Windows Control Panel > Programs and Features or the Sentinel Admin Control Center)
  2. 2. Navigate to the Thales support portal at supportportal.thalesgroup.com
  3. 3. Download Sentinel LDK Runtime version 10.22 or later
  4. 4. Back up any existing Sentinel LDK configuration and license data
  5. 5. Run the installer for version 10.22 to update the Runtime
  6. 6. Restart any affected services or applications that use the Sentinel LDK Runtime
  7. 7. Verify the new version is installed correctly and the XSS vulnerability is resolved

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3457 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3457 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data