github.com/sigstore/cosign
Affected
- introduced
0, fixed3.0.5(semver)
Fixed versions
3.0.5
Fix
- Fixed version
3.0.5go get github.com/sigstore/[email protected]
Advisory
Also known as: BIT-cosign-2026-24122, CVE-2026-24122, GO-2026-4529
Cosign considered signatures valid with expired intermediate certificates when transparency log verification is skipped
Summary
When verifying artifact signatures using a certificate, Cosign first verifies the certificate chain using the leaf certificate's "not before" timestamp and later checks expiry of the leaf certificate using either a signed timestamp provided by the Rekor transparency log or from a timestamp authority, or using the current time. The root and all issuing certificates are assumed to be valid during the leaf certificate's validity. An issuing certificate with a validity that expires before the leaf certificate will be considered valid during verification even if the provided timestamp would mean the issuing certificate should be considered expired.
Impact
No impact to users of the public Sigstore infrastructure. This may affect private deployments with customized PKIs. In practice, this is unlikely to occur as CAs should not be issuing certificates that outlive the validity of the CA and its parents.
Workarounds
Upgrade to the latest release, or verify the certificate chain out of band.
Example to Reproduce
Low Basis: The source's own band: LOW
0, fixed 3.0.5 (semver)3.0.5
3.0.5go get github.com/sigstore/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0