Skip to main content
VulnerabilityPublished Updated

CVE-2026-27190: denoland deno · OS Command Injection

Affects denoland denoSource CVE Database V5

0
Compare

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

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
2.4% chance of exploitation in 30 days – higher than 84% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.6.8
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 20 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 29 Oct 2026.

What to do

Upgrade denoland deno to 2.6.8.

Affected software

ProductAffectedFixed in
denolanddenoAffected
  • <2.6.8
Fixed in
  • 2.6.8

AI-suggested

To mitigate CVE-2026-27190, organizations should immediately upgrade all Deno installations to version 2.6.8 or later, where the vulnerability is patched. Beyond patching, developers should implement strict input validation and sanitization for any data passed to child process commands to prevent injection of malicious payloads. Avoid constructing OS commands from untrusted input or use safer APIs that do not invoke shell commands directly. Employ the principle of least privilege by running Deno processes with minimal permissions and in isolated environments or containers to limit potential damage. Monitor logs and network traffic for unusual child process invocations or command execution patterns. Incorporate security testing and code reviews focusing on command injection risks in development workflows. Finally, maintain an up-to-date inventory of Deno versions in use across the organization to ensure timely patch management.

Description

Deno is a JavaScript, TypeScript, and WebAssembly runtime. Prior to 2.6.8, a command injection vulnerability exists in Deno's node:child_process implementation. This vulnerability is fixed in 2.6.8.

References

Community reviews

Loading reviews…