CVE-2026-119290: high-severity vulnerability in zuke-build zuke
Zuke: Resolved secret() values are written to GITHUB_STEP_SUMMARY in the clear, disclosing them to anyone who can view the workflow run
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.5epss 0.5%
Zuke is a code-first, strongly typed build automation system for Deno. Prior to 1.51.0, @zuke/core writes rendered reportSummary(...) notes to GITHUB_STEP_SUMMARY through writeJobSummary without applying the redactor that protects resolved secret() values in console and persisted run output. A GitHub Actions build that places secret-derived text in a summary note can publish credentials in cleartext to everyone able to view the workflow run, including unauthenticated viewers of a public repository, and the durable summary remains exposed until the run is deleted. GitHub Actions masking directives do not protect the summary file, while runs outside GitHub Actions and builds that do not summarize secret-derived text are not affected. This issue is fixed in version 1.51.0.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Affected products
zuke-build · zukeRelated CVEs — zuke-build zuke
In the same product, most dangerous first.
CVE-2026-119287HIGHZuke: Command-form registry descriptors bypass the MCP launch policyEPSS 0.2%CVE-2026-119288HIGHZuke: Argument injection on Windows: batch shims are launched through cmd.exe, which re-parses the command lineEPSS 0.2%CVE-2026-119289HIGHZuke: githubWorkflow adopts any workflow run whose title matches its marker, so anyone who can dispatch the workflow can satisfy or block a release gateEPSS 0.2%CVE-2026-119291MEDIUMzuke setup and zuke import follow symbolic links planted at scaffold names, allowing writes outside the target directoryEPSS 0.1%