CVE-2026-32260
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDeno is a JavaScript, TypeScript, and WebAssembly runtime. From 2.7.0 to 2.7.1, A command injection vulnerability exists in Deno's node:child_process polyfill (shell: true mode) that bypasses the fix for CVE-2026-27190. The two-stage argument sanitization in transformDenoShellCommand (ext/node/polyfills/internal/child_process.ts) has a priority bug: when an argument contains a $VAR pattern, it is wrapped in double quotes (L1290) instead of single quotes. Double quotes in POSIX sh do not suppress backtick command substitution, allowing injected commands to execute. An attacker who controls arguments passed to spawnSync or spawn with shell: true can execute arbitrary OS commands, bypassing Deno's permission system. This vulnerability is fixed in 2.7.2.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA command injection vulnerability in Deno's node:child_process polyfill (versions 2.7.0-2.7.1) uses incorrect quote wrapping for arguments containing $VAR patterns—double quotes instead of single quotes. Since POSIX sh double quotes don't suppress backtick command substitution, attackers controlling spawn/spawnSync arguments with shell:true can execute arbitrary OS commands, bypassing Deno's permission system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2.7.0, < 2.7.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check your installed Deno versionRun `deno --version` in your terminal and note the version numberAffected if The version displayed is 2.7.0 or 2.7.1 (versions 2.7.2 and later are not affected)
-
Identify usage of node:child_process polyfillSearch your codebase for imports of `node:child_process` or `npm:child_process` modules, and identify any spawn or spawnSync function callsAffected if Your code imports and uses spawn or spawnSync from the child_process polyfill
-
Verify if shell:true option is usedExamine all spawn and spawnSync calls found in your code and check whether the third argument (options object) contains `shell: true`Affected if Any spawn/spawnSync call has shell:true enabled - this is required for the vulnerability to be exploitable
-
Inspect arguments passed to spawn/spawnSyncReview the arguments array passed to spawn/spawnSync calls and determine whether any come from untrusted sources such as user input, network requests, or environment variablesAffected if Arguments to spawn/spawnSync with shell:true can contain user-controlled or untrusted data (especially strings starting with $)
-
Check for $VAR patterns in argumentsAudit the argument values passed to spawn/spawnSync with shell:true for any that contain dollar signs followed by variable names (e.g., $HOME, $PATH, $USER) which would be interpreted as shell variable expansionAffected if Arguments containing $VAR patterns are passed to spawn/spawnSync with shell:true - these could be expanded by the shell due to the double-quote wrapping bug
You are affected if you run Deno 2.7.0 or 2.7.1 and your code uses node:child_process spawn or spawnSync with shell:true and passes arguments containing $ patterns from untrusted sources.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.7.2
Upgrade to Deno 2.7.2 or later; until then, avoid shell:true in child_process functions and strictly validate all arguments passed to spawn/spawnSync.
2.7.2
- Upgrade Deno to version 2.7.2 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32260 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-32260 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data