Skip to main content
CVE-2025-59705VulnerabilityPublished Updated

CVE-2025-59705: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 6.8 Medium · fixed in 13.6.12 : update affected systems when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
6.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 13.6.12
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

AI-suggested

1. Enforce strict physical security controls around HSM devices, including locked cabinets, surveillance, and access logging to prevent unauthorized physical proximity or tampering. 2. Implement tamper-evident seals and chassis intrusion detection mechanisms to alert on unauthorized hardware access attempts. 3. Restrict personnel access to only trusted and vetted individuals with a clear need to access HSM hardware. 4. Monitor system boot processes and USB interface status for anomalies that could indicate unauthorized reactivation attempts. 5. 6. Conduct regular security audits and penetration tests focusing on physical security and hardware interface protections. 7. Consider deploying additional layers of cryptographic key protection, such as multi-factor authentication for key usage or key splitting, to reduce risk if an HSM is compromised. 8. Review and update incident response plans to include scenarios involving physical tampering of cryptographic hardware.

Description

Entrust nShield Connect XC, nShield 5c, and nShield HSMi through 13.6.11, or 13.7 (patched in 13.6.12 (LTS) and 13.9.0 (STS)), allow a Physically Proximate Attacker to Escalate Privileges by enabling the USB interface through chassis probe insertion during system boot, aka "Unauthorized Reactivation of the USB interface" or F01.

References

Community reviews

Loading reviews…