🛡️ CVE-2025-59698 — nshield-5c-firmware

How this vulnerability can be exploited

This issue can be reached with physical access to the device, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity high, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

• Attack vector: Physical — the attacker has to touch the device.
• Attack complexity: Low — the attack works reliably, with no preparation.
• Privileges required: None — an unauthenticated stranger can try it.
• User interaction: None — nobody has to be tricked into anything.
• Scope: Unchanged — the damage stays inside the vulnerable component.
• Confidentiality impact: High — total loss, or loss the attacker controls.
• Integrity impact: High — total loss, or loss the attacker controls.
• Availability impact: High — total loss, or loss the attacker controls.

Weakness class

CVE-2025-59698 is classified as CWE-1270: Generation of Incorrect Security Tokens. The product implements a Security Token mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. However, the Security Tokens generated in the system are incorrect.

Affected software

CVE-2025-59698 is recorded against 5 packages.

• nshield-5c-firmware (from 13.7 up to 13.9.0)
• nshield-connect-xc-base-firmware (from 13.7 up to 13.9.0)
• nshield-connect-xc-high-firmware (from 13.7 up to 13.9.0)
• nshield-connect-xc-mid-firmware (from 13.7 up to 13.9.0)
• nshield-hsmi-firmware (from 13.7 up to 13.9.0)

Timeline and source

Published on 2 December 2025 and last revised on 17 June 2026. A public exploit is known to exist, which raises the urgency of patching considerably. Record sourced from NVD.

References

github.com
www.entrust.com
github.com

Other advisories for this package

nshield-5c-firmware has other advisories on record. If you are patching this one, these are worth checking on the same host:

• CVE-2025-59702 (7.2 High, published 2 Dec 2025)
• CVE-2025-59694 (6.8 Medium, published 2 Dec 2025)
• CVE-2025-59701 (4.1 Medium, published 2 Dec 2025)
• CVE-2025-59693 (9.8 Critical, published 2 Dec 2025)
• CVE-2025-59700 (3.9 Low, published 2 Dec 2025)
• CVE-2025-59699 (6.8 Medium, published 2 Dec 2025)
• CVE-2025-59705 (6.8 Medium, published 2 Dec 2025)
• CVE-2025-59697 (7.2 High, published 2 Dec 2025)

Same weakness in other software

These advisories are the same class of weakness (CWE-1270: Generation of Incorrect Security Tokens) in other software:

• CVE-2026-15831 (5.0 Medium, published 17 Aug 2026)
• CVE-2026-49499 (8.8 High, published 22 Jul 2026)
• CVE-2023-32188 (9.5 Critical, published 16 Oct 2024)
• CVE-2023-22644 (5.5 Medium, published 20 Sep 2023)
• CVE-2023-2882 (9.8 Critical, published 25 May 2023)
• CVE-2023-30524 (4.3 Medium, published 12 Apr 2023)
• CVE-2014-2237 (8.0 High, published 17 May 2022)

Details

Affected Packages

References