dbcve.org
Nshield 5c FirmwareOperating system · Entrust

CVE-2025-59695

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
Entrust nShield Connect XC, nShield 5c, and nShield HSMi through 13.6.11, or 13.7, allow a user with OS root access to alter firmware on the Chassis Management Board (without Authentication). This is called F04.

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

A vulnerability in Entrust nShield Connect XC, nShield 5c, and nShield HSMi allows authenticated users with OS root-level access to modify firmware on the Chassis Management Board without any authentication, enabling potential persistent compromise of the hardware security module.

MitigationRestrict physical and logical access to HSM devices to trusted personnel only, and apply vendor-provided firmware updates beyond versions 13.6.11/13.7 which address this authentication bypass in the Chassis Management Board.

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 HSM model and firmware version
    Access the HSM management interface or use the vendor-provided CLI tool (typically 'fwverify' or via the nShield management utilities) to retrieve the current firmware version installed on the device
    Affected if The firmware version is either below 13.6.12, or falls within the range 13.7.3 to 13.9.0 (exclusive of 13.9.0)
  2. Determine if OS root-level access is possible
    Review user access controls and audit logs to determine whether any user account has root-level operating system access on the HSM, including any service accounts or administrative interfaces that provide OS-level privileges
    Affected if Any authenticated user possesses root-level OS access to the HSM device
  3. Verify Chassis Management Board configuration
    Examine the HSM configuration for the Chassis Management Board settings, typically accessible via the HSM's web management interface or serial console, to confirm whether firmware modification operations are logged or restricted
    Affected if The Chassis Management Board allows firmware modifications without requiring additional authentication beyond OS root access

Your environment is affected if the installed firmware version matches the vulnerable ranges (< 13.6.12 or >= 13.7.3 to < 13.9.0) AND any user has root-level OS access to the HSM device.

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

Restrict physical and logical access to HSM devices to trusted personnel only, and apply vendor-provided firmware updates beyond versions 13.6.11/13.7 which address this authentication bypass in the Chassis Management Board.

Recommended fix High confidence

Upgrade to firmware >= 13.6.12 (for versions < 13.6.12) or >= 13.9.0 (for versions >= 13.7.3)

  1. 1. Identify the current firmware version of the affected nShield device (5c, HSMi, or Connect XC)
  2. 2. Determine which firmware branch is currently installed (< 13.6.12 or >= 13.7.3, < 13.9.0)
  3. 3. For devices on firmware < 13.6.12: Upgrade to firmware version 13.6.12 or later
  4. 4. For devices on firmware >= 13.7.3 and < 13.9.0: Upgrade to firmware version 13.9.0 or later
  5. 5. Obtain the firmware update from Entrust's official support portal or authorized distribution channels
  6. 6. Follow Entrust's standard firmware upgrade procedure, ensuring proper power supply and backup of configuration
  7. 7. After upgrade, verify the firmware version and confirm the vulnerability is remediated
Caveat Review Entrust release notes for any configuration or compatibility changes in the target firmware 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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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