dbcve.org
Nshield 5c FirmwareOperating system · Entrust

CVE-2025-59693

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-02
Fix available
A fix is available. Upgrade to 13.6.12 / 13.9.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable 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
The Chassis Management Board in Entrust nShield Connect XC, nShield 5c, and nShield HSMi through 13.6.11, or 13.7, allows a physically proximate attacker to obtain debug access and escalate privileges by bypassing the tamper label and opening the chassis without leaving evidence, and accessing the JTAG connector. This is called F02.

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

Physical security bypass in Entrust nShield HSM chassis allowing attackers to circumvent tamper labels, open the device without leaving evidence, and access the JTAG connector to obtain debug access and escalate privileges.

MitigationApply vendor patches for versions 13.6.11 or 13.7; implement strict physical access controls around HSM devices to prevent unauthorized chassis access.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Nshield 5c FirmwareOperating system
Affected:< 13.6.12>= 13.7.3, < 13.9.0
Nshield Hsmi FirmwareOperating system
Affected:< 13.6.12>= 13.7.3, < 13.9.0
Nshield Connect Xc Base FirmwareOperating system
Affected:< 13.6.12>= 13.7.3, < 13.9.0
Nshield Connect Xc Mid FirmwareOperating system
Affected:< 13.6.12>= 13.7.3, < 13.9.0
Nshield Connect Xc High FirmwareOperating system
Affected:< 13.6.12>= 13.7.3, < 13.9.0

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 nShield HSM model
    Locate the physical device or check inventory records to determine if you have an Entrust nShield 5c, nShield HSMi, or nShield Connect Xc (Base/Mid/High) unit.
    Affected if Device is any of these models listed in the affected products.
  2. Check nShield 5c firmware version
    Access the device management interface or use the nShield CLI utility (run 'nversion' or check via the nShield Security World software) to retrieve the firmware version.
    Affected if Version is below 13.6.12, or is 13.7.3 or higher but below 13.9.0.
  3. Check nShield HSMi firmware version
    Access the HSMi management interface or use the diagnostic tools provided with the nShield software to retrieve the firmware version.
    Affected if Version is below 13.6.12, or is 13.7.3 or higher but below 13.9.0.
  4. Check nShield Connect Xc firmware version
    Access the Connect Xc web interface or use the nShield management utilities to retrieve the base/mid/high firmware version.
    Affected if Version is below 13.6.12, or is 13.7.3 or higher but below 13.9.0.
  5. Inspect physical tamper labels
    Visually examine all tamper-evident labels on the HSM chassis for signs of breakage, removal, or resealing. Check for any physical evidence of unauthorized chassis opening.
    Affected if Tamper labels show evidence of removal or the device chassis has been opened without proper authorization logging.

You are affected if you have an Entrust nShield 5c, HSMi, or Connect Xc device running firmware version below 13.6.12, or between 13.7.3 and 13.8.x inclusive, and the device chassis has been potentially accessed physically.

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
Upgrade available Upgrade to 13.6.12 / 13.9.0 or later
Fixed in 13.6.1213.9.0
Interim mitigation

Apply vendor patches for versions 13.6.11 or 13.7; implement strict physical access controls around HSM devices to prevent unauthorized chassis access.

Recommended fix High confidence

Upgrade to nShield firmware version 13.9.0 or later (or 13.6.12 if staying on the 13.6.x branch)

  1. 1. Identify the specific nShield product model (5c, HSMi, or Connect XC variant) currently deployed
  2. 2. Determine the current firmware version by accessing the HSM management interface or using the nShield command line utilities
  3. 3. Download the firmware update from Entrust's official support portal at www.entrust.com or the Entrust nShield customer support channels
  4. 4. Follow Entrust's official firmware upgrade procedure documented in the nShield Installation and Configuration Guide
  5. 5. Verify the firmware upgrade was successful by confirming the new version displays >= 13.9.0 or 13.6.12
  6. 6. Ensure physical security controls (tamper evident labels) are inspected and replaced if damaged post-upgrade
Caveat Review Entrust release notes for any compatibility changes between current version and target version before upgrading

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

Fix this in Nshield 5c Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59693 — 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-2025-59693 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