Skip to main content
CVE-2025-59699VulnerabilityPublished Updated

CVE-2025-59699: 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 25 Oct 2026, 19:02 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 26% 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-25.

What to do

AI-suggested

To mitigate CVE-2025-59699, organizations should implement the following specific measures: 1) Disable Legacy GRUB Bootloader support or configure it to disallow booting from external USB devices unless explicitly authorized. 2) Enable secure boot mechanisms where supported to ensure only trusted firmware and bootloaders are executed. 3) Physically secure HSM devices in locked, access-controlled environments with surveillance and logging to prevent unauthorized physical access. 4) Regularly audit and verify bootloader configurations and firmware versions to detect insecure defaults or unauthorized changes. 5) Implement strict operational procedures for maintenance personnel, including supervision and access logging. 6) Coordinate with Entrust for firmware updates or patches addressing this vulnerability once available. 7) Consider network segmentation and monitoring to detect anomalous activity that could indicate compromise of HSMs. 8) Conduct security awareness training for staff on the risks of physical attacks and insider threats related to HSMs.

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 booting from a USB device with a valid root filesystem. This occurs because of insecure default settings in the Legacy GRUB Bootloader.

References

Community reviews

Loading reviews…