Zuke: Argument injection on Windows: batch shims are launched through cmd.exe, which re-parses the command line
Only affects @zuke/core before 1.51.0 on Windows builds that run a wrapper through a local .cmd or .bat shim in node_modules/.bin. Fixed in 1.51.0.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 1.51.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Zuke, a Deno-based build automation system, is affected on Windows when it runs tools from node_modules/.bin through cmd.exe. Attacker-influenced input containing special characters can cause an extra attacker-chosen command to run with the build's credentials and access.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Zuke is a code-first, strongly typed build automation system for Deno. Prior to 1.51.0, @zuke/core launches resolved Windows .cmd and .bat shims by prepending cmd /c, causing cmd.exe to reparse a command line assembled with C-runtime quoting rules. A build running on Windows that resolves a tool from node_modules/.bin and passes attacker-influenced text containing an unquoted &, |, or ^ metacharacter can execute an additional attacker-chosen command in the build's context with access to its credentials. POSIX platforms are not affected. This issue is fixed in version 1.51.0.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- zuke-build zuke
fixed in 1.51.0
References 4
GitHub · zuke-build/zuke
Questions about CVE-2026-119288
What does this mean?
On Windows, batch shims are launched through cmd.exe, which parses the command line again. Attacker-chosen text placed in wrapper arguments can therefore lead to additional commands running in the build's own context, with whatever credentials that build holds.Source: github.com
Am I affected, and how do I check?
The issue involves @zuke/core versions before 1.51.0, on Windows only. It applies when a build resolves a wrapper's binary from node_modules/.bin and a local .cmd or .bat shim exists there. To check, look at the installed @zuke/core version in node_modules/@zuke/core/package.json and list any .cmd or .bat files in node_modules/.bin.Source: github.com
What should I do about it?
Upgrade to @zuke/core 1.51.0. The vendor's advisory also says that, on Windows runners, untrusted text should not be interpolated into wrapper arguments, and the tool can be pinned to a non-batch executable with .toolPath(...).Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data