cosign: Cosign provides code signing and transparency for containers and binaries
CVE-2026-24122 is fixed in 3 products on 1 platform, first by DEBIAN-CVE-2026-24122, released February 19, 2026. It is not reported as exploited. Patch Radar priority: Routine.
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.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| cosign · Debian 14 | 3.0.6-1 | DEBIAN-CVE-2026-24122 | Feb 19, 2026 |
| cosign · opensuse-leap 15.6 | 3.0.5-150400.3.35.1 | SUSE-SU-2026:0777-1 | Mar 3, 2026 |
| cosign · opensuse-leap 16.0 | 3.0.5-160000.1.1 | OPENSUSE-SU-2026:20386-1 | Mar 18, 2026 |
| cosign · sles 15.7 | 3.0.5-150400.3.35.1 | SUSE-SU-2026:0777-1 | Mar 3, 2026 |
| cosign · sles 16.0 | 3.0.5-160000.1.1 | SUSE-SU-2026:20904-1 | Mar 18, 2026 |
| govulncheck-vulndb · opensuse-leap 15.6 | 0.0.20260226T182644-150000.1.149.1 | SUSE-SU-2026:0757-1 | Mar 3, 2026 |
| govulncheck-vulndb · opensuse-leap 16.0 | 0.0.20260723T184607-160000.1.1 | OPENSUSE-SU-2026:21483-1 | Jul 30, 2026 |
| trivy · opensuse-leap 16.0 | 0.74.0-160000.2.1 | OPENSUSE-SU-2026:21801-1 | Sep 7, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.