Message disclosure and forgery via AEAD nonce reuse
Published Nov 21, 2025 · Updated Nov 21, 2025
AEAD nonce reuse in dajiaji hpke-js before 1.7.5 allows remote attackers to disclose or forge messages through concurrent Seal() calls. SenderContextImpl computes a nonce from its sequence number, awaits asynchronous encryption, and increments the sequence only afterward, so overlapping calls use the same nonce. Exploitation requires two Seal() operations to overlap on one sender context; the reused nonce breaks confidentiality and integrity for the resulting ciphertexts.
Summary
What happened
AEAD nonce reuse in dajiaji hpke-js before 1.7.5 allows remote attackers to disclose or forge messages through concurrent Seal() calls. SenderContextImpl computes a nonce from its sequence number, awaits asynchronous encryption, and increments the sequence only afterward, so overlapping calls use the same nonce. Exploitation requires two Seal() operations to overlap on one sender context; the reused nonce breaks confidentiality and integrity for the resulting ciphertexts.
The record
- CVE
- CVE-2025-64767
- Published
- Nov 21, 2025
- Updated
- Nov 21, 2025
- Vendor
- dajiaji
- Product
- hpke-js
- Classifications
- CWE-323
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 21, 2025CVE publishedPublication date reported by the CVE source.
- Nov 21, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.7.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-73g8-5h73-26h4 concurrent Seal() proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo