CVE-2026-102289
High 7.0No known exploitationFix status unknownTitle not yet published
Record last updated
CVSS score
High on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Higher than 16% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
zizmor is a static analysis tool for CI/CD systems. In version 1.27.0, debug logging serializes the parsed application configuration with a derived Debug implementation for GitHubToken, causing credentials supplied through GH_TOKEN, GITHUB_TOKEN, ZIZMOR_GITHUB_TOKEN, --gh-token, --github-token, or --zizmor-github-token to be written to stderr in cleartext. A single -v or --verbose option or an applicable RUST_LOG directive enables the affected logging during normal online operation and --no-online-audits, while explicit --offline clears the token first. If another party can read a CI log, support artifact, terminal capture, or public bug report containing the output, the party can use the credential according to its scopes, repository access, and lifetime. This vulnerability is fixed in 1.28.0.
Weakness: CWE-532
Patching and mitigation
- Patch status
- Unknown: no source documents a fix
- Mitigation
- None documented
- Vendor guidance
- No vendor link on record
Affected products
No affected products documented yet.
Timeline
- No dated events documented yet.
Vendor guidance and references
- https://github.com/zizmorcore/zizmor/commit/0731e01706af273be860d3d221e4d122e6741b6f (opens in a new tab)
- https://github.com/zizmorcore/zizmor/commit/724d0e86f4c073c3dc64507fb6c39bc20e46a48f (opens in a new tab)
- https://github.com/zizmorcore/zizmor/pull/2213 (opens in a new tab)
- https://github.com/zizmorcore/zizmor/pull/2215 (opens in a new tab)
- https://github.com/zizmorcore/zizmor/releases/tag/v1.28.0 (opens in a new tab)
- https://github.com/zizmorcore/zizmor/security/advisories/GHSA-f42p-wjw5-97qh (opens in a new tab)