zizmor: Debug logging prints available GitHub credentials in cleartext

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

7.0 · CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:A/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H · score source

EPSS

• CVE-2026-102289: 0.24% estimated exploitation activity in the next 30 days; percentile 15.76 (FIRST EPSS, 2026-11-10). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary zizmor 1.27.0 exposes GitHub access tokens in cleartext when debug-level logging is enabled. Tokens supplied via environment variables (`GH_TOKEN`, `GITHUB_TOKEN`, `ZIZMOR_GITHUB_TOKEN`), or the corresponding command-line options (`--gh-token`, `--github-token`, `--zizmor-github-token`) are included in the debug representation of the parsed application configuration and written to stderr. The affected logging is enabled by a single `-v`/`--verbose` or an applicable `RUST_LOG` directive.

Details The issue was introduced in commit 919bea46, merged through PR #2180. Version `1.26.1` and earlier are unaffected. Version `1.27.0` is the first and only affected release. zizmor accepts GitHub credentials to perform authenticated GitHub API requests for the purposes of retrieving remote GitHub repositories and performing online audits that…

Published by the source

9 Nov 2026, 21:56 UTC

Last modified by the source

9 Nov 2026, 22:00 UTC

Source last checked

10 Nov 2026, 06:35 UTC

1. Revision 2 · amended · 10 Nov 2026

   Amended from osv record GHSA-f42p-wjw5-97qh

2. Revision 1 · created · 9 Nov 2026

   Published from ghsa record GHSA-f42p-wjw5-97qh

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-102289

Advisory: zizmor: Debug logging prints available GitHub credentials in cleartext
IDs: CVE-2026-102289, GHSA-f42p-wjw5-97qh
Record: https://patchnext.com/advisories/cve-2026-102289 (revision 2, source checked 10 Nov 2026, 06:35 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: zizmor 1.28.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI zizmor: affected >= 1.27.0, < 1.28.0; fixed in 1.28.0

## Suggested inspection (read-only)
- `python -m pip show zizmor`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on zizmor.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-f42p-wjw5-97qh (GitHub-reviewed advisory GHSA-f42p-wjw5-97qh lists affected ranges: PyPI zizmor >=1.27.0 <=1.27.0)
- Verified: https://osv.dev/vulnerability/GHSA-f42p-wjw5-97qh (OSV record GHSA-f42p-wjw5-97qh lists affected ranges: PyPI zizmor >=1.27.0 <1.28.0 (fixed))

Commands are suggestions: review each one before running it.