Spoofable workflow run matching in Zuke githubWorkflow gate
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- High
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- None · High · Low
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-345.
Summary
Zuke before 1.10.0 is a code-first build automation system for Deno, and its @zuke/gh githubWorkflow gate matches dispatched workflow runs only by a display-title marker. When the external workflow repository grants workflow_dispatch to a party the releasing repository does not fully trust, an attacker can copy that marker, dispatch a run, and have the gate adopt its conclusion without checking the event, ref, or creation window (CWE-345). A passing run can authorize an unvalidated release, and a failed or cancelled run can block a valid one.
Written with Claude Haiku 5.5 from the sources below · 2026-10-30
Description from the CNA
Zuke is a code-first, strongly typed build automation system for Deno. Prior to 1.10.0, the @zuke/gh githubWorkflow(...) gate correlates a dispatched workflow run using only a display-title marker that is visible in the workflow run list and can be copied by another dispatcher. In configurations where the external workflow repository grants workflow_dispatch permission to a party not equally trusted by the releasing repository, an attacker can dispatch a run with the marker and cause the gate to adopt its conclusion without verifying the event, ref, or creation window. A passing substituted run can authorize an unvalidated release, while a failed or cancelled run can block a valid release, and the persisted adopted run ID preserves the substitution across build resume. This issue is fixed in version 1.10.0.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| zuke-build | zuke | before 1.10.0 | 1.10.0 | Patch available | CNA |
- zuke Vendorzuke-build Affected before 1.10.0 Fixed in 1.10.0 Patch available CNA
Remediation
Upgrade Zuke to version 1.10.0, which fixes this issue.
Written with Claude Haiku 5.5 from the sources below · 2026-10-30
- Fix · CNA zuke (zuke-build) Fixed in 1.10.0
Timeline
- 2026-10-30 Threatist record created from CVE-2026-119289
- 2026-11-01 Priority changed: MEDIUM → LOW
- 2026-11-06 CISA SSVC decision points changed
References
More zuke-build vulnerabilities
- TI-2026-83202 Zuke writes resolved secrets in cleartext to GitHub step summaries CVSS 3.1HIGH 7.5
- TI-2026-83198 Zuke: Command-form registry descriptors bypass the MCP launch policy CVSS 3.1HIGH 8.0
- TI-2026-83199 Argument injection in Zuke on Windows via cmd.exe batch shims CVSS 3.1HIGH 7.0
- TI-2026-83203 Symlink following in zuke setup and import allows outside writes CVSS 3.1MEDIUM 5.5
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences