FKIE_CVE-2026-24122

Vulnerability from fkie_nvd - Published: 2026-02-19 23:16 - Updated: 2026-02-20 19:04
Severity ?
3.7 (Low) - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
Summary
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.
References
security-advisories@github.comhttps://github.com/sigstore/cosign/commit/3c9a7363f563db76d78e2de2cabd945450f3781ePatch
security-advisories@github.comhttps://github.com/sigstore/cosign/releases/tag/v3.0.5Product, Release Notes
security-advisories@github.comhttps://github.com/sigstore/cosign/security/advisories/GHSA-wfqv-66vq-46rmExploit, Vendor Advisory
Impacted products
Vendor Product Version
sigstore cosign *
To clipboard 

{
  "configurations": [
    {
      "nodes": [
        {
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:sigstore:cosign:*:*:*:*:*:*:*:*",
              "matchCriteriaId": "309BB1C3-3537-4989-AFA4-24ADFAD25F96",
              "versionEndExcluding": "3.0.5",
              "vulnerable": true
            }
          ],
          "negate": false,
          "operator": "OR"
        }
      ]
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "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\u0027s \"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\u0027s 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."
    },
    {
      "lang": "es",
      "value": "Cosign proporciona firma de c\u00f3digo y transparencia para contenedores y binarios. En las versiones 3.0.4 e inferiores, un certificado emisor con una validez que expira antes que el certificado hoja se considerar\u00e1 v\u00e1lido durante la verificaci\u00f3n, incluso si la marca de tiempo proporcionada significar\u00eda que el certificado emisor deber\u00eda considerarse expirado. Al verificar firmas de artefactos usando un certificado, Cosign primero verifica la cadena de certificados usando la marca de tiempo \u0027no antes de\u0027 del certificado hoja y luego verifica la caducidad del certificado hoja usando una marca de tiempo firmada proporcionada por el registro de transparencia de Rekor o de una autoridad de marca de tiempo, o usando la hora actual. Se asume que el certificado ra\u00edz y todos los certificados emisores son v\u00e1lidos durante la validez del certificado hoja. No hay impacto para los usuarios de la infraestructura p\u00fablica de Sigstore. Esto puede afectar a despliegues privados con PKIs personalizadas. Este problema ha sido corregido en la versi\u00f3n 3.0.5."
    }
  ],
  "id": "CVE-2026-24122",
  "lastModified": "2026-02-20T19:04:02.700",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "HIGH",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 3.7,
          "baseSeverity": "LOW",
          "confidentialityImpact": "NONE",
          "integrityImpact": "LOW",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 2.2,
        "impactScore": 1.4,
        "source": "security-advisories@github.com",
        "type": "Secondary"
      }
    ]
  },
  "published": "2026-02-19T23:16:24.517",
  "references": [
    {
      "source": "security-advisories@github.com",
      "tags": [
        "Patch"
      ],
      "url": "https://github.com/sigstore/cosign/commit/3c9a7363f563db76d78e2de2cabd945450f3781e"
    },
    {
      "source": "security-advisories@github.com",
      "tags": [
        "Product",
        "Release Notes"
      ],
      "url": "https://github.com/sigstore/cosign/releases/tag/v3.0.5"
    },
    {
      "source": "security-advisories@github.com",
      "tags": [
        "Exploit",
        "Vendor Advisory"
      ],
      "url": "https://github.com/sigstore/cosign/security/advisories/GHSA-wfqv-66vq-46rm"
    }
  ],
  "sourceIdentifier": "security-advisories@github.com",
  "vulnStatus": "Analyzed",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-295"
        }
      ],
      "source": "security-advisories@github.com",
      "type": "Primary"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.