CVE-2026-24122: Github.com/sigstore/cosign Cosign Considered Signatures Valid With Vulnerability

LOW
Advisory Identifier: GHSA-wfqv-66vq-46rm
CVSS 3.7
CWE-295
Published
Advisory Summary

CVE-2026-24122 is a LOW (CVSS 3.7) cosign considered signatures valid with vulnerability (CWE-295: Improper Certificate Validation) affecting Github.com/sigstore/cosign libraries in the Go ecosystem. The issue involves cosign considered signatures valid with expired intermediate certificates when transparency log verification is skipped. Remediation is available by upgrading affected packages to version 3.0.5.

CVE-2026-24122 at a Glance

CVE Identifier CVE-2026-24122
GHSA Identifier GHSA-wfqv-66vq-46rm
Severity LOW
CVSS v3.1 Base Score 3.7
CWE Classification CWE-295: Improper Certificate Validation
Affected Product Github.com/sigstore/cosign
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 3.7

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-24122

To remediate this vulnerability, upgrade all affected Github.com/sigstore/cosign dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/sigstore/cosign fixed: 3.0.5
Upgrade github.com/sigstore/cosign to 3.0.5
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/sigstore/cosign

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-24122, inspect your project dependencies for Github.com/sigstore/cosign:

inspect dependencies for github.com/sigstore/cosign

Analyze the terminal output to locate any version of Github.com/sigstore/cosign in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.0.5), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-295: Improper Certificate Validation, where the product does not validate, or incorrectly validates, a certificate. In Github.com/sigstore/cosign, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## 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

CVE-2026-24122 Affected Github.com/sigstore/cosign Versions

1 component(s)
Fixed Versions:
3.0.5
Product / Package Ecosystem Affected Versions Fixed Version
github.com/sigstore/cosign
Go
< 3.0.5
3.0.5

References

Frequently Asked Questions

What is CVE-2026-24122?
CVE-2026-24122 is a security vulnerability in Github.com/sigstore/cosign involving Cosign considered signatures valid with expired intermediate certificates when transparency log verification is skipped under CWE-295: Improper Certificate Validation.
Which Github.com/sigstore/cosign versions are affected?
Affected versions include releases prior to 3.0.5 across affected packages: github.com/sigstore/cosign.
What version fixes CVE-2026-24122?
Upgrading to 3.0.5 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/sigstore/cosign affected?
Yes, github.com/sigstore/cosign is affected in releases prior to 3.0.5. Upgrade your dependency to 3.0.5 or later.
What is the CVSS score of CVE-2026-24122?
CVE-2026-24122 has a CVSS v3.1 base score of 3.7 (LOW) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N.
What CWE is associated with CVE-2026-24122?
CVE-2026-24122 is classified under CWE-295: Improper Certificate Validation (The product does not validate, or incorrectly validates, a certificate.).
How can I check Go dependencies for CVE-2026-24122?
Run the dependency tree command: 'inspect dependencies for github.com/sigstore/cosign'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-wfqv-66vq-46rm",
  "modified" : "2026-02-20T16:43:55Z",
  "published" : "2026-02-19T22:09:12Z",
  "aliases" : [ "CVE-2026-24122" ],
  "summary" : "Cosign considered signatures valid with expired intermediate certificates when transparency log verification is skipped",
  "details" : "## Summary\n\nWhen 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.\n\n## Impact\n\nNo 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.\n\n## Workarounds\n\nUpgrade to the latest release, or verify the certificate chain out of band.\n\n## Example to Reproduce\n\n* Root CA certificate is valid from 12pm-2pm\n* Intermediate CA certificate is valid from 12:30pm-1:30pm\n* 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\n* Signature generated at 2:30pm with a signed timestamp\n* 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\n* 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\n* Even though the root and intermediate would be expired at 2:30pm, verification succeeds",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/sigstore/cosign"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.0.5"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 3.0.4"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/sigstore/cosign/security/advisories/GHSA-wfqv-66vq-46rm"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-24122"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/sigstore/cosign/commit/3c9a7363f563db76d78e2de2cabd945450f3781e"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/sigstore/cosign"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/sigstore/cosign/releases/tag/v3.0.5"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-295" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-02-19T22:09:12Z",
    "nvd_published_at" : "2026-02-19T23:16:24Z"
  }
}