EM-20261109-AKM4
VulnerabilityHigh severity
zizmor Vulnerability (CVE-2026-102289)
CVE-2026-102289
Status
Developing
Since : signals keep joining.
- First Signal
- Nov 09 21:56 UTCC26 GitHub Advisory Database
- Page Born
- Nov 09 22:18 UTCsecond source joined
- Last Signal
- Nov 09 22:18 UTC3 hours before snapshot
- Sources
- 20 official · 2 research, news or crowd
- Open For
- 2 hoursso far
Life Of This Page
- 1BornA second, independent source names it.
- 2Developing · NowNew signals join; severity can move.
- 3ConfirmedNot yetCISA KEV lists it, or exploitation in the wild is reported.
- 4ResolvedNot yetPast the fix deadline and 14 days with no new signal.
- 5ArchivedNot yet30 days after resolved. Read only; the link keeps working. Reopens if it comes back.
The ID never changes, and earlier addresses keep working. A correction is logged, never overwritten. If two pages turn out to be one incident, the later one points to the earlier.
Vulnerability Lifecycle
- Disclosed: reachedNov 09 22:18 UTCC6 NVD published
- Scored: reachedNov 09 22:18 UTCCVSS 7
- Exploited: not yetNot yetNo exploitation reported
- Advisories: not yetNot yetNone yet
- Vendor Response: not yetNot yetNone in sources yet
- Resolved: not yetNot yetAfter 14 quiet days
Timeline
Point at a mark to read it. Squares are signals, colored by severity; every one is also listed under Signals.
Signals
- CVE-2026-102289 (CVSS 7) (opens source in a new tab) 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… High severityDatabaseC6 NVD CVE API 2.0
- GHSA-f42p-wjw5-97qh / CVE-2026-102289: zizmor: Debug logging prints available GitHub credentials in cleartext (opens source in a new tab) pip:zizmor High severityDatabaseC26 GitHub Advisory Database