VulnerabilityPublished 20 Nov 2025Updated 21 Nov 2025

CVE-2025-64767: @hpke/core reuses AEAD nonces

Affects @hpke/coreSource GCVE Database

Compare

Authoritative record:CVE-2025-64767· Critical 9.1

Not known to be exploited · CVSS 9.1 Critical : upgrade to 1.7.5 as a priority.

Data as of 15 Nov 2026, 01:53 UTC

CVSS 3.1 base score

9.1Critical

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (GitHub_M)	CVSS 3.1	9.1

Patch: Available – fixed in 1.7.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

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

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
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: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 14 Nov 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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

Upgrade @hpke/core to 1.7.5.

Affected software

Product	Affected	Fixed in
npm@hpke/core	Affected <1.7.5	Fixed in 1.7.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to @hpke/core version 1.7.5 or later, where this race condition and nonce reuse issue has been fixed. Until upgrading, ensure that Seal() and Open() calls on the same context are not executed concurrently by implementing synchronization to serialize these operations.

Description

The @hpke/core library has a race condition in its SenderContext Seal() API that causes reuse of AEAD nonces during concurrent Seal() calls. This nonce reuse violates AEAD security guarantees, leading to complete loss of confidentiality and integrity of encrypted messages. The issue affects versions prior to 1.7.5 and has been fixed in version 1.7.5.

Impact

Exploitation of this vulnerability allows attackers to observe or manipulate encrypted messages due to nonce reuse in AEAD encryption, resulting in a complete loss of confidentiality and integrity of the messages produced by the Seal() API. This compromises the security guarantees of the HPKE implementation in @hpke/core prior to version 1.7.5.

Summary

The @hpke/core package's SenderContext Seal() method has a concurrency flaw where multiple asynchronous Seal() calls can compute the same AEAD nonce due to a race condition on the sequence number. This results in nonce reuse in the AEAD encryption, which is explicitly insecure and can compromise message confidentiality and integrity. The vulnerability is confirmed by a proof-of-concept demonstrating identical ciphertexts for concurrent encryptions of the same plaintext. The recommended fix is to serialize Seal() and Open() calls per context to prevent nonce reuse. The issue is tracked as CVE-2025-64767 and fixed in version 1.7.5.

CWE-323Reusing a Nonce, Key Pair in Encryption (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
Nonces should be used for the present occasion and only once.
Implementation
Refuse to reuse nonce values.
Implementation
Use techniques such as requiring incrementing, time based and/or challenge response to assure uniqueness of nonces.
OWASP Cheat Sheets
Forgot Password (opens in a new tab)
Transport Layer Protection (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
Cryptographic Storage (opens in a new tab)
OWASP ASVS 4.0.3
V2.3.1 (opens in a new tab)
V2.6.2 (opens in a new tab)
V2.7.6 (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

Affected software

Description

AI analysisMachine-generated, updated 15 Nov 2026, 01:53 UTC

WeaknessesCWE-323

Technical details

References

Community reviews

Related threats