CVE-2026-24122

Name	CVE-2026-24122
Description	Cosign provides code signing and transparency for containers and binaries. In versions 3.0.4 and below, 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. 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. There is no impact to users of the public Sigstore infrastructure. This may affect private deployments with customized PKIs. This issue has been fixed in version 3.0.5.
Source	CVE (at NVD; CERT, ENISA, LWN, oss-sec, fulldisc, Debian ELTS, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more)
Debian Bugs	1128652

Vulnerable and fixed packages

The table below lists information on source packages.

Source Package	Release	Version	Status
cosign (PTS)	forky, trixie	2.5.0-2	vulnerable
	sid	2.6.2-1	vulnerable

The information below is based on the following data on fixed versions.

Package	Type	Release	Fixed Version	Urgency	Origin	Debian Bugs
cosign	source	(unstable)	(unfixed)			1128652

Notes

[trixie] - cosign <no-dsa> (Minor issue)
https://github.com/sigstore/cosign/security/advisories/GHSA-wfqv-66vq-46rm
Fixed by: https://github.com/sigstore/cosign/commit/3c9a7363f563db76d78e2de2cabd945450f3781e (v3.0.5)