CVE-2026-119289

Zuke: githubWorkflow adopts any workflow run whose title matches its marker, so anyone who can dispatch the workflow can satisfy or block a release gate

Published Oct 30, 2026 CVSS 3.1 · 7.1 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

Zuke, a build automation system for Deno, has a flaw in its GitHub workflow gate that matches dispatched runs only by a display title marker, ignoring the origin of the event, its reference, or its creation time. An attacker who can trigger a workflow dispatch can create a run whose title meets the marker; the gate then adopts the outcome of that run. This bypass allows malicious or untrusted users to authorize releases that have not been properly validated or to block legitimate releases, constituting an authorization bypass that aligns with CWE‑345.

Affected Systems

Zuke build automation system from zuke-build, specifically versions prior to 1.10.0, uses the vulnerable @zuke/gh githubWorkflow gate.

Risk and Exploitability

The CVSS score of 7.1 indicates high severity; the EPSS score is not available, and the vulnerability does not appear in the CISA KEV catalog. The likely attack vector is remote via the GitHub workflow_dispatch API. Any user with workflow_dispatch permission for the external workflow repository can dispatch a run that satisfies the marker, making the gate accept its outcome and enabling attackers to approve or block releases without proper validation, thereby compromising release integrity and possibly providing a foothold for further malicious activity.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Zuke to version 1.10.0 or later.
  • Restrict workflow_dispatch permissions on the external workflow repository to trusted users or accounts only.
  • Implement monitoring and verification for workflow runs, ensuring that only expected runs are accepted by the gate or adding checks for event source and reference.

Generated by OpenCVE AI on October 30, 2026 at 17:26 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Zuke-build
Zuke-build zuke
Vendors & Products Zuke-build
Zuke-build zuke
Type Values Removed Values Added
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.
Title Zuke: githubWorkflow adopts any workflow run whose title matches its marker, so anyone who can dispatch the workflow can satisfy or block a release gate
Weaknesses CWE-345
References
Metrics cvssV3_1

{'score': 7.1, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:L'}

Weaknesses
  • CWE-345

    Insufficient Verification of Data Authenticity

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 6, 2026, 4:13 PM
Reserved
Oct 29, 2026, 6:50 PM
Status
Deferred
Published
Oct 30, 2026, 4:17 PM
Modified
Nov 6, 2026, 5:17 PM