Skip to main content
VulnerabilityPublished

CVE-2026-22864: denoland deno · Command Injection

Affects denoland denoSource CVE Database V5

0

Not known to be exploited · CVSS 8.1 High : upgrade to 2.5.6 soon.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.5.6
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Upgrade deno and denoland/deno to 2.5.6.

Affected software

ProductAffectedFixed in
denolanddenoAffected
  • <2.5.6
Fixed in
  • 2.5.6
GitHubdenoland/denopkg:github/denoland/denoOther threatsAffected
  • <2.5.6
Fixed in
  • 2.5.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-22864, European organizations should immediately upgrade all Deno installations to version 2.5.6 or later, where the case-insensitive extension check is properly implemented. Additionally, organizations should audit scripts and tooling that spawn child processes to ensure they do not rely on vulnerable Deno versions or unsafe command execution patterns. Implement strict input validation and sanitization for any user-supplied data used in command spawning. Employ application whitelisting to restrict execution of unauthorized batch or shell scripts. Monitor logs for suspicious process spawning activities, especially those involving batch files with unusual casing. Network segmentation and endpoint protection can limit lateral movement if exploitation occurs. Finally, maintain up-to-date asset inventories to identify all Deno runtime deployments across Windows environments and apply patches promptly. Security teams should prepare incident response plans for potential exploitation scenarios involving command injection.

Description

Deno is a JavaScript, TypeScript, and WebAssembly runtime. Before 2.5.6, a prior patch aimed to block spawning Windows batch/shell files by returning an error when a spawned path’s extension matched .bat or .cmd. That check performs a case-sensitive comparison against lowercase literals and therefore can be bypassed when the extension uses alternate casing (for example .BAT, .Bat, etc.). This vulnerability is fixed in 2.5.6.

References

Community reviews

Loading reviews…