CVE-2025-64767 json
hpke-js reuses AEAD nonces
published 2025-11-20 11 mo ago modified 2026-10-18 21 d ago also GHSA-73g8-5h73-26h4 , EUVD-2025-198319
- cvss
- 9.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 13%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 11 mo ago
Exploit prediction
0.23% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
| GitHub | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | @hpke/core | <1.7.5 |
1.7.5 |
Affected products
- dajiaji hpke-js
Classification
- Weakness
-
- CWE-323 Reusing a Nonce, Key Pair in Encryption
References
-
github.com
/dajiaji/hpke-js/commit/94a767c9b9f37ce48d5cd86f7017d8cacd294aaf
web
-
github.com
/dajiaji/hpke-js/security/advisories/GHSA-73g8-5h73-26h4
web
-
github.com
/dajiaji/hpke-js/blob/b7fd3592c7c08660c98289d67c6bb7f891af75c4/packages/core/src/senderContext.ts#L22-L34
web
-
nvd.nist.gov
/vuln/detail/CVE-2025-64767
advisory
-
github.com
/dajiaji/hpke-js
package
Sources
- CVE List CVE-2025-64767
- GitHub Advisory GHSA-73g8-5h73-26h4
- NVD CVE-2025-64767
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.