Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Cosign Certificate Chain Expiry Validation Issue Allows Issuing Certificate Expiry to Be Overlooked

CVSS 3.1 3.7 LOWEUVD CVSS 3.1 3.7 CVSS 3.1 · [email protected] · Secondary 3.7 LOWCVSS_V3 Publisher rating LOWFixed by github.com/sigstore/cosign 3.0.5osv · severity unknownFixed by github.com/sigstore/cosign/v3 3.0.5KEV status unknown

cve-program · CVE-2026-24122

Published

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.

Read the publisher's advisory

euvd · EUVD-2026-8430

Published

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.

Read the publisher's advisory

nvd · CVE-2026-24122

Published

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.

Read the publisher's advisory

osv · GHSA-wfqv-66vq-46rm

Published

## 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 * Root CA certificate is valid from 12pm-2pm * Intermediate CA certificate is valid from 12:30pm-1:30pm * Leaf certificate is valid from 1pm-3pm - **Note that this is unlikely to happen in practice**, as a CA shouldn't issue a certificate that would be valid after the issuing CA certificate expires * Signature generated at 2:30pm with a signed timestamp * During verification, the leaf certificate's not before time (1pm) is used to verify the chain - 1pm is in the validity windows for the root and intermediate CA certificates * The timestamp's time is checked to be in the validity window of only the leaf certificate - 2:30pm is in the validity window for the leaf * Even though the root and intermediate would be expired at 2:30pm, verification succeeds

Read the publisher's advisory

osv · GO-2026-4529

Published

Cosign considered signatures valid with expired intermediate certificates when transparency log verification is skipped in github.com/sigstore/cosign

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-24122

Published

cosign

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "sigstore",
                    "product": "cosign",
                    "versions": [
                        {
                            "version": "< 3.0.5",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2026-8430

Published

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

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2026-24122

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Analyzed

Weakness classifications: CWE-295

Original publisher date fields

published: 2026-02-19T23:16:24.517

lastModified: 2026-06-17T10:22:39.833

1 source CPE criteria · context only
  • cpe:2.3:a:sigstore:cosign:*:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-wfqv-66vq-46rm

Published

github.com/sigstore/cosign

Go

SEMVER · introduced 0 → fixed 3.0.5

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GO-2026-4529

Published

github.com/sigstore/cosign

Go

SEMVER · introduced 0

github.com/sigstore/cosign/v2

Go

SEMVER · introduced 0

github.com/sigstore/cosign/v3

Go

SEMVER · introduced 0 → fixed 3.0.5

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 15 Nov 23:13 UTC · 274 of 275 readable · 250 fully read · 18 waiting for GitHub's hourly limit · documentation 461/469 current