CVE-2025-64767VulnerabilityPublished 21 Nov 2025

CVE-2025-64767: dajiaji hpke-js · Reusing a Nonce, Key Pair in Encryption

Affects dajiaji hpke-jsSource CVE Database V5

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

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

9.1Critical

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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
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 2026-10-25.

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 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 dajiaji/hpke-js to 1.7.5.

Affected software

Product	Affected	Fixed in
npmdajiaji/hpke-js`pkg:npm/dajiaji/hpke-js`Other threats	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

The primary mitigation is to upgrade all instances of hpke-js to version 1.7.5 or later, where the race condition and nonce reuse issue have been fixed. Organizations should audit their codebases and dependencies to identify any usage of hpke-js and verify the version in use. For environments where immediate upgrade is not feasible, implementing strict concurrency controls around Seal() calls to prevent simultaneous invocations may reduce risk temporarily, though this is not a substitute for patching. Additionally, organizations should monitor network traffic and logs for anomalous patterns that could indicate exploitation attempts. Incorporating cryptographic best practices such as key rotation and layered encryption can also help limit exposure. Finally, informing development teams about safe usage patterns and the importance of timely updates is critical to prevent recurrence.

Description

hpke-js is a Hybrid Public Key Encryption (HPKE) module built on top of Web Cryptography API. Prior to version 1.7.5, the public SenderContext Seal() API has a race condition which allows for the same AEAD nonce to be re-used for multiple Seal() calls. This can lead to complete loss of Confidentiality and Integrity of the produced messages. This issue has been patched in version 1.7.5.

Impact

For European organizations, the impact of this vulnerability is severe. Any system using vulnerable versions of hpke-js for encrypting sensitive communications or data is at risk of having encrypted messages decrypted or altered by attackers, leading to loss of confidentiality and integrity. This can result in exposure of personal data protected under GDPR, intellectual property theft, fraud, or disruption of secure communications. Sectors such as finance, healthcare, government, and critical infrastructure that rely on secure messaging or cryptographic protections are particularly vulnerable. The vulnerability's remote exploitability and lack of need for authentication increase the risk of widespread exploitation. Additionally, compromised cryptographic assurances can undermine trust in digital services and lead to regulatory penalties if data breaches occur. The absence of known exploits currently provides a window for proactive mitigation, but the critical nature demands immediate action.

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 21 Nov 2025, 19:11 UTC

WeaknessesCWE-323

Technical details

References

Community reviews

Related threats