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.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 1
- First seenCVSS 7.5 · zuke-buildNVD modified 2026-10-30 15:50
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 4
- https://github.com/zuke-build/zuke/security/advisories/GHSA-42wp-rrh6-vc23 x_refsource_confirm
- https://github.com/zuke-build/zuke/pull/547 x_refsource_misc
- https://github.com/zuke-build/zuke/commit/a46fd7287c913d937b4d0bb46d0c22b87ddd8ba7 x_refsource_misc
- https://github.com/zuke-build/zuke/releases/tag/core-v1.51.0 x_refsource_misc