Improper cipher finalization in Deno node:crypto allows infinite encryptions
In Deno versions prior to 2.6.0, the Node.js compatibility crypto layer (node:crypto) fails to properly finalize cipher objects. Specifically, calling cipher.final() does not correctly conclude/close the cipher state; the cipher can remain active (e.g., a Cipheriv object remains usable with internal buffering state still accessible) rather than transitioning to a closed CipherBase state. This enables an attacker to perform repeated/infinite encryptions using the same cipher context, which can be leveraged for brute-force and more refined cryptanalytic attacks aimed at learning server secrets. The issue is fixed in Deno 2.6.0.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical cryptographic state-management flaw in Deno’s Node.js compatibility layer (node:crypto) where cipher.final() does not properly finalize/close the cipher, leaving internal state/buffers accessible and enabling attacks aimed at learning server secrets.
A cryptographic implementation flaw in Deno (node:crypto) where cipher finalization does not occur prior to 2.6.0, enabling unlimited encryptions and potentially facilitating brute-force or cryptanalytic attacks aimed at recovering server secrets.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.