CVE-2026-22863: denoland deno · Missing Cryptographic Step
Affects denoland denoSource CVE Database V5
Not known to be exploited · CVSS 9.2 Critical : upgrade to 2.6.0 as a priority.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.6.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 15 Jan 2026
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-26.
What to do
Upgrade deno and denoland/deno to 2.6.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| denolanddeno | Affected
| Fixed in
|
GitHubdenoland/denopkg:github/denoland/denoOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
European organizations should immediately upgrade all Deno runtime environments to version 2.6.0 or later to ensure the cryptographic finalization step is correctly implemented. Conduct a comprehensive inventory of applications and services using Deno, focusing on those performing cryptographic operations. Review and audit all cryptographic code to confirm that encryption and decryption processes are correctly handled and do not rely on vulnerable versions. Implement network-level protections such as Web Application Firewalls (WAFs) and intrusion detection systems (IDS) to monitor for anomalous encryption-related traffic patterns indicative of brute force or cryptanalysis attempts. Employ strict access controls and segmentation to limit exposure of systems running vulnerable Deno versions. Establish monitoring and alerting for unusual cryptographic operation volumes or failures. Coordinate with software vendors and development teams to ensure timely patch deployment and secure coding practices. Finally, update incident response plans to include scenarios involving cryptographic vulnerabilities and potential data exfiltration.
Description
Deno is a JavaScript, TypeScript, and WebAssembly runtime. Before 2.6.0, node:crypto doesn't finalize cipher. The vulnerability allows an attacker to have infinite encryptions. This can lead to naive attempts at brute forcing, as well as more refined attacks with the goal to learn the server secrets. This vulnerability is fixed in 2.6.0.