What is the CVSS score of CVE-2026-24122?

CVE-2026-24122 has a CVSS 3.1 base score of 3.7 (Low). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N. EPSS exploitation probability: 0.0%.

Which versions of Cosign are affected by CVE-2026-24122?

CVE-2026-24122 is a low-severity vulnerability (CVSS 3.7). The limited severity suggests constrained impact, typically requiring specific conditions or local access for exploitation.. A patch is available.

Is there a public PoC exploit available for CVE-2026-24122?

Yes, a public proof-of-concept exploit is available for CVE-2026-24122. Prioritise patching immediately. EPSS: 0.0%.

How to fix or mitigate CVE-2026-24122?

During next maintenance window: Apply vendor patches when convenient. Vendor patch is available.

Cosign CVE-2026-24122

LOW

Improper Certificate Validation (CWE-295)

2026-02-19 security-advisories@github.com

GHSA-wfqv-66vq-46rm

Authentication Bypass Cosign Sigstore

3.7

CVSS 3.1 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

3.7 LOW

AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

None

Lifecycle Timeline

Analysis Generated

Mar 12, 2026 - 22:03 vuln.today

PoC Detected

Feb 20, 2026 - 19:04 vuln.today

Public exploit code

Patch released

Feb 20, 2026 - 19:04 nvd

Patch available

CVE Published

Feb 19, 2026 - 23:16 nvd

LOW 3.7

DescriptionGitHub Advisory

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.

AnalysisAI

Cosign provides code signing and transparency for containers and binaries. [CVSS 3.7 LOW]

Technical ContextAI

Classified as CWE-295 (Improper Certificate Validation). Affects Cosign. 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