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.
How to fix
- sigstore cosign3.0.5 or later
- github.com/sigstore/cosign3.0.5 or later
- github.com/sigstore/cosign/v33.0.5 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| sigstore cosign | v < 3.0.5 | 3.0.5 |
| github.com/sigstore/cosignGo | v < 3.0.5, No range specified | 3.0.5 |
| github.com/sigstore/cosign/v2Go | No range specified | — |
| github.com/sigstore/cosign/v3Go | v < 3.0.5 | 3.0.5 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.