CVE-2026-119290

Zuke: Resolved secret() values are written to GITHUB_STEP_SUMMARY in the clear, disclosing them to anyone who can view the workflow run

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

Analysis

AI-generated

Technical impact

Zuke is a code‑first build automation system for Deno that writes a rendered report summary to the GITHUB_STEP_SUMMARY file. Prior to version 1.51.0, the @zuke/core library failed to redact resolved secret() values when publishing those summaries, a flaw classified as CWE‑532. The result is that any secret‑derived text included in a JavaScript object that is rendered in a summary note is written to the summary file in plain text.

Affected Systems

The issue affects any installation of @zuke/core that is older than 1.51.0 and any GitHub Actions workflow that writes a summary note through the writeJobSummary function. Public repositories, or repositories where workflow run pages are viewable without authentication, are particularly vulnerable because the summary file is accessible to all viewers of the run. Builds that do not generate a summary note or run outside of GitHub Actions are not affected.

Risk and Exploitability

The CVSS score of 7.5 indicates high severity, while an EPSS score is not available, so the likelihood of exploitation is uncertain. The vulnerability is listed in the CISA KEV catalog as not present, but the attack vector is clear: an unauthenticated viewer of a public workflow run can read the GITHUB_STEP_SUMMARY file and extract any credentials that were accidentally included in a summary note. Exploitation requires only that the workflow run produce a summary that contains secret‑derived text; no additional credentials or vulnerabilities are needed to access the payload.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Zuke to version 1.51.0 or later where the secret redactor is applied to summary output.
  • Modify build steps so that any summary notes do not contain secret‑derived text; remove or mask secret references before invoking writeJobSummary.
  • If an upgrade cannot be performed immediately, restrict workflow run visibility or delete runs that have potentially exposed credentials, and monitor for evidence of credential leakage.

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

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
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
Metrics ssvc

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

Type Values Removed Values Added
Description 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.
Title Zuke: Resolved secret() values are written to GITHUB_STEP_SUMMARY in the clear, disclosing them to anyone who can view the workflow run
Weaknesses CWE-532
References
Metrics cvssV3_1

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

Weaknesses
  • CWE-532

    Insertion of Sensitive Information into Log File

Sources

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