Secret disclosure via reusable finalized cipher state
Published Jan 15, 2026 · Updated Jan 15, 2026
Cryptographic state handling in Deno before 2.6.0 allows remote attackers to recover server secrets through repeated cipher use. The node:crypto Cipheriv and Decipheriv objects fail to record that final() completed, so later update() or final() calls reuse the native cipher context. Exploitation requires an application to expose attacker-influenced access to a persistent cipher object; repeated encryption supports brute-force or refined secret-recovery attacks.
Summary
What happened
Cryptographic state handling in Deno before 2.6.0 allows remote attackers to recover server secrets through repeated cipher use. The node:crypto Cipheriv and Decipheriv objects fail to record that final() completed, so later update() or final() calls reuse the native cipher context. Exploitation requires an application to expose attacker-influenced access to a persistent cipher object; repeated encryption supports brute-force or refined secret-recovery attacks.
The record
- CVE
- CVE-2026-22863
- Published
- Jan 15, 2026
- Updated
- Jan 15, 2026
- Vendor
- Deno Land Inc.
- Product
- Deno
- Classifications
- CWE-325
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 15, 2026CVE publishedPublication date reported by the CVE source.
- Jan 15, 2026Record 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=< 2.6.0
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
- Vendor cipher-finalization reproductionproof 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