VulnerabilityPublished 2 Dec 2025Updated 26 Aug 2026

CVE-2025-59698: Generation of Incorrect Security Tokens

Source CVE Database V5

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, 13:47 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

Attack Vector: Physical
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief or persistent.
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Enforce strict physical security controls around all Entrust nShield HSM devices, including locked server rooms, surveillance, and access logging.
Implement tamper-evident seals and regular physical inspections to detect unauthorized access attempts.
Limit personnel with physical access to trusted and trained staff only.
Monitor device logs and environmental sensors for signs of tampering or unusual activity.
Develop and test incident response plans specific to hardware security breaches.
Engage with Entrust to obtain information on forthcoming patches or firmware updates addressing this vulnerability.
Plan for hardware upgrades or replacements to versions not affected by this vulnerability, especially for devices running legacy bootloaders.
Consider deploying additional layers of cryptographic key protection, such as multi-factor authentication for key usage or key splitting, to reduce risk if keys are exposed.
Review and update asset inventories to identify all affected devices and prioritize remediation efforts.
Educate staff about the risks of physical attacks on cryptographic hardware and the importance of vigilance.

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)), might allow a physically proximate attacker to gain access to the EOL legacy bootloader.

Impact

For European organizations, this vulnerability poses a substantial risk to entities that depend on Entrust nShield HSMs for critical cryptographic operations, such as financial institutions, government agencies, and critical infrastructure providers. If exploited, attackers with physical access could extract cryptographic keys or manipulate cryptographic processes, leading to data breaches, unauthorized transactions, or disruption of secure communications. This could undermine trust in digital services, cause regulatory compliance violations (e.g., GDPR), and result in financial and reputational damage. The physical access requirement limits the attack scope to environments where attackers can get close to the hardware, such as data centers, branch offices, or poorly secured facilities. However, insider threats or sophisticated adversaries targeting high-value assets could leverage this vulnerability. The lack of available patches means organizations must rely on physical security controls and operational mitigations until a vendor fix is released. The impact is particularly critical for sectors with stringent security requirements and high-value cryptographic assets.

CWE-1270Generation of Incorrect Security Tokens (opens in a new tab)
Base weakness
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.
Architecture and Design · Implementation
Generation of Security Tokens should be reviewed for design inconsistency and common weaknesses.; Security-Token definition and programming flow should be tested in pre-silicon and post-silicon testing.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
Attack patterns
Exploit Non-Production Interfaces (opens in a new tab)
Token Impersonation (opens in a new tab)
Exploitation of Improperly Controlled Hardware Security Identifiers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 9 Dec 2025, 16:47 UTC

WeaknessesCWE-1270

Technical details

References

Community reviews

Related threats