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…
Historical advisory saved 11 Nov 2026 06:32:30 UTC. The publisher may have updated it since then. Latest advisory.
euvd · EUVD-2026-8430
PublishedCosign 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.
Additional publisher context
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Feb 19, 2026, 10:27:08 PM
dateUpdated: Feb 20, 2026, 3:41:03 PM
8 related source bulletins · separate from aliases
openSUSE-SU-2026:11676-1: trivy-0.74.0-2.1 on GA media
CVE-2026-24122 · CVE-2026-37236 · CVE-2026-41178 · CVE-2026-50163
SUSE-SU-2026:20904-1: Security update for cosign
CVE-2025-11065 · CVE-2025-58181 · CVE-2026-22703 · CVE-2026-22772 · CVE-2026-23991 · CVE-2026-23992 · CVE-2026-24122 · CVE-2026-24137 · CVE-2026-26958
SUSE-SU-2026:0777-1: Security update for cosign
CVE-2025-11065 · CVE-2025-58181 · CVE-2026-22703 · CVE-2026-22772 · CVE-2026-23991 · CVE-2026-23992 · CVE-2026-24122 · CVE-2026-24137 · CVE-2026-26958
openSUSE-SU-2026:10635-1: hauler-1.4.2-1.1 on GA media
CVE-2026-24122
openSUSE-SU-2026:20386-1: Security update for cosign
CVE-2025-11065 · CVE-2025-58181 · CVE-2026-22703 · CVE-2026-22772 · CVE-2026-23991 · CVE-2026-23992 · CVE-2026-24122 · CVE-2026-24137 · CVE-2026-26958
openSUSE-SU-2026:10235-1: cosign-3.0.5-1.1 on GA media
CVE-2026-22772 · CVE-2026-23991 · CVE-2026-23992 · CVE-2026-24122 · CVE-2026-24137 · CVE-2026-26958
openSUSE-SU-2026:21801-1: Security update for trivy
CVE-2026-24122 · CVE-2026-37236 · CVE-2026-41178 · CVE-2026-50163 · CVE-2026-56854 · CVE-2026-56855 · CVE-2026-78662 · CVE-2026-84303 · CVE-2026-84304 · CVE-2026-84445
openSUSE-SU-2026:20662-1: Security update for hauler
CVE-2026-24122
- Source published
- Feb 19, 2026, 10:27:08 PM (timezone not stated)
- Source modified
- Feb 20, 2026, 3:41:03 PM (timezone not stated)
- Saved here
- 11 Nov 2026 06:32:30 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
EUVD CVSS 3.1 · 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N