Is github.com/sigstore/cosign affected by CVE-2026-24122?

Go github.com/sigstore/cosign is affected in >=0.

Is CVE-2026-24122 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.2%.

medium

CVE-2026-24122

Go · github.com/sigstore/cosign • Go · github.com/sigstore/cosign/v2 • Go · github.com/sigstore/cosign/v3

Summary

Cosign considered signatures valid with expired intermediate certificates when transparency log verification is skipped in github.com/sigstore/cosign

Severity: medium
EPSS: 0.2% (p10)
Also known as: GHSA-wfqv-66vq-46rm, BIT-cosign-2026-24122, GO-2026-4529, GO-2026-4529#github.com/sigstore/cosign, GO-2026-4529#github.com/sigstore/cosign/v2, GO-2026-4529#github.com/sigstore/cosign/v3
Published: 2026-02-23

References

Related advisories

CVE-2026-39395 — medium · Go/github.com/sigstore/cosign
CVE-2026-22703 — medium · Go/github.com/sigstore/cosign

Is your project exposed to this? Stateward checks every dependency on every pull request and flags it only if your code actually reaches it.

Check my repo

Summarize with AI

ChatGPT Claude Perplexity

Sources: CISA KEV (public domain), OSV.dev & GitHub Advisory Database (CC-BY-4.0), FIRST EPSS, NVD/CWE (public domain). Served live from the Stateward advisory database.