Debug logging in zizmor prints GitHub tokens in cleartext
Key facts
- Attack vector
- Local
- Privileges required
- None
- User interaction
- Active
- Attack complexity
- Low
- Attack requirements
- Present
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA and GitHub. Impact type from CWE-532.
Summary
zizmor version 1.27.0 writes GitHub tokens in cleartext to stderr during debug logging, because the GitHubToken type derives its Debug output. The flaw is classified as CWE-532, insertion of sensitive information into a log file. Anyone who can read a CI log, support artifact, terminal capture or public bug report containing that output can use the token according to its scopes, repository access and lifetime. Enabling verbose or debug logging triggers the output during normal online operation.
Written with Claude Haiku 5.5 from the sources below · 2026-11-14
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| zizmorcore | zizmor | = 1.27.0 | — | No fix listed | CNA |
| — | zizmor (PyPI) | 1.27.0 to before 1.28.0 | 1.28.0 | Patch available | GHSA-f42p-wjw5-97qh |
- zizmor Vendorzizmorcore Affected = 1.27.0 Fixed in — No fix listed CNA
- zizmor (PyPI) Vendor— Affected 1.27.0 to before 1.28.0 Fixed in 1.28.0 Patch available GHSA-f42p-wjw5-97qh
Remediation
Upgrade the zizmor PyPI package to version 1.28.0, the fixed version listed for this flaw. The sources list 1.27.0 as the affected version for zizmorcore zizmor with no fix listed.
Written with Claude Haiku 5.5 from the sources below · 2026-11-14
- Fix · GHSA-f42p-wjw5-97qh zizmor (PyPI) Fixed in 1.28.0 Advisory →
Timeline
- 2026-11-09 Threatist record created from CVE-2026-102289
- 2026-11-09 Alias added: GHSA-f42p-wjw5-97qh
- 2026-11-09 Fix available: PyPI/[email protected] · GHSA-f42p-wjw5-97qh
- 2026-11-09 CVSS score added · GHSA-f42p-wjw5-97qh
- 2026-11-09 Weakness changed · GHSA-f42p-wjw5-97qh
- 2026-11-09 7 new references · GHSA-f42p-wjw5-97qh
- 2026-11-11 Priority changed: MEDIUM → LOW
- 2026-11-14 CISA SSVC decision points changed
References
Other 7
- https://github.com/zizmorcore/zizmor/security/advisories/GHSA-f42p-wjw5-97qh
- https://github.com/zizmorcore/zizmor/pull/2213
- https://github.com/zizmorcore/zizmor/pull/2215
- https://github.com/zizmorcore/zizmor/commit/0731e01706af273be860d3d221e4d122e6741b6f
- https://github.com/zizmorcore/zizmor/commit/724d0e86f4c073c3dc64507fb6c39bc20e46a48f
- https://github.com/zizmorcore/zizmor/releases/tag/v1.28.0
- https://github.com/zizmorcore/zizmor
Sources
- CVE-2026-102289 · CVE Program
- CVE-2026-102289 · NVD
- FIRST EPSS
- GHSA-f42p-wjw5-97qh · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences