CVE-2026-119290
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.
Executive briefing
This record describes a reported software or hardware weakness. The description and CVSS rating are source metadata; practical risk depends on whether your environment uses an affected product/version and whether the vulnerable component is reachable and configured in an exploitable way.
Severity & exploitability
CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Impacted products and platforms
Specific affected product configurations are not currently available in the NVD record. Review vendor advisories and validate applicability against your asset inventory.
How it works and what it could affect
The NVD description is the authoritative short summary currently available for this record. A detailed technical mechanism is not inferred when the source record does not provide one.
Weakness classification: CWE-532
Review the CVSS attack characteristics above to understand whether exploitation is network/local, whether privileges or user interaction are required, and which confidentiality, integrity or availability impacts are scored.
Remediation and recommended response
- Identify exposure: compare the affected product and version ranges below with your asset inventory, software bill of materials, endpoint inventory and externally exposed services.
- Remediate: review the linked vendor security advisory or patch notes, upgrade to a fixed release, or apply the vendor-provided workaround if an upgrade cannot be completed.
- Mitigate while patching: restrict network access to the vulnerable service, disable the affected feature where operationally safe, and monitor vendor/CERT advisories for updated guidance.
- Validate: confirm the fixed version or mitigation on representative systems, run a vulnerability rescan, and retain change evidence.
Vendor remediation / security advisories
- security-advisories@github.com — vendor
- security-advisories@github.com — vendor
- security-advisories@github.com — vendor
- security-advisories@github.com — vendor
- security-advisories@github.com — vendor
- security-advisories@github.com — vendor
- security-advisories@github.com — vendor
- security-advisories@github.com — vendor
Exploit intelligence & references
No CISA KEV match is recorded in the latest successful catalog refresh. This is not a guarantee that public proof-of-concept code or exploitation does not exist.
- security-advisories@github.com vendor
- security-advisories@github.com vendor
- security-advisories@github.com vendor
- security-advisories@github.com vendor
Sources: NVD and CISA KEV when available. Vendor confirmation remains the final authority for fixed versions and workarounds.