Skip to main content
VulnerabilityPublished

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

Affects denoland denoSource CVE Database V5

0
Compare

Mentioned vulnerabilities

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

Data as of 30 Oct 2026, 11:52 UTC

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

What to do

Upgrade denoland deno to 2.7.2.

Affected software

ProductAffectedFixed in
denolanddenoAffected
  • >=2.7.0 <2.7.2
Fixed in
  • 2.7.2
GitHubdenoland/denopkg:github/denoland/denoOther threatsAffected
  • =2.7.0
  • =2.7.1
Fixed in–

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

AI-suggested

  1. Immediate upgrade to Deno version 2.7.2 or later, where the vulnerability is fixed.
  2. Audit all codebases and dependencies to identify usage of spawn or spawnSync with shell: true in the child_process polyfill and refactor to avoid shell invocation when possible.
  3. Implement strict input validation and sanitization on any arguments passed to these functions, especially those containing environment variable patterns or special shell characters.
  4. Employ runtime monitoring and anomaly detection to identify suspicious command execution patterns indicative of exploitation attempts.
  5. Restrict permissions and isolate environments running Deno applications to limit potential damage from command injection.
  6. Educate developers about the risks of shell: true usage and encourage safer alternatives such as direct command execution without shell interpretation.
  7. Review and update security policies to include regular dependency vulnerability scanning and timely patching of runtime environments.

Description

CVE-2026-32260 is a high-severity OS command injection vulnerability in Deno versions 2.7.0 and 2.7.1 affecting the node:child_process polyfill when used with shell: true. The flaw arises from improper sanitization of arguments containing $VAR patterns, where double quotes are used instead of single quotes, allowing backtick command substitution in POSIX shells. This enables attackers controlling spawn or spawnSync arguments to execute arbitrary OS commands, bypassing Deno's permission system. The vulnerability was introduced as a regression after a previous fix (CVE-2026-27190) and is resolved in version 2.7.2.

References

Community reviews

Loading reviews…