CVE-2026-119289 Details
Description
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.
A vulnerability exists in Zuke, a build automation system for Deno, in versions prior to 1.10.0. The issue arises within the '@zuke/gh' package, specifically in the 'githubWorkflow(...)' gate, which uses a display-title marker to correlate dispatched workflow runs. This marker can be easily copied and does not authenticate the run. In scenarios where the external workflow repository allows 'workflow_dispatch' permission to untrusted parties, an attacker can exploit this by dispatching a run with the marker. The gate will then adopt the run's conclusion without verifying key details, such as the event, reference, or creation window. As a result, a passing run can authorize an unvalidated release, while a failed or canceled run can block a legitimate one. This vulnerability is particularly concerning because the adopted run ID is persisted, allowing the substitution to survive across build resumes.
Users can upgrade to Zuke version 1.10.0, which addresses the vulnerability by implementing a more robust correlation process for workflow runs. The updated version ensures that the gate only adopts runs that are genuinely dispatched by the user, on the correct reference, and within the appropriate time window.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Oct 30, 2026CISA-ADP
Assessed Nov 6, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/zuke-build/zuke/commit/4257b0bc5ef5e387a44f913349646d4baccd1654 | [email protected] | Source CodeVendor |
| https://github.com/zuke-build/zuke/pull/542 | [email protected] | Issue TrackingVendor |
| https://github.com/zuke-build/zuke/releases/tag/gh-v1.10.0 | [email protected] | Release NotesVendor |
| https://github.com/zuke-build/zuke/security/advisories/GHSA-rrc8-3g8p-cm8p | [email protected] | AdvisoryRemedyVendor |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-345 | Insufficient Verification of Data Authenticity | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| Zuke | < 1.10.0 (semver) |
CPE
Remediation
| |
| Zuke Build @zuke/gh | < 1.10.0 (semver) |
CPE
Remediation
| |
Change History
2 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Nov 6, 2026 | CVE Modified | CISA-ADP |
| Oct 30, 2026 | New CVE Received | [email protected] |
Volerion