CVE-2026-22703

{
  "id": "CVE-2026-22703",
  "cveTags": [],
  "metrics": {
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2026-22703",
          "role": "CISA Coordinator",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "no"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "version": "2.0.3",
          "timestamp": "2026-01-12T16:43:50.752285Z"
        }
      }
    ],
    "cvssMetricV31": [
      {
        "type": "Secondary",
        "source": "security-advisories@github.com",
        "cvssData": {
          "scope": "UNCHANGED",
          "version": "3.1",
          "baseScore": 5.5,
          "attackVector": "LOCAL",
          "baseSeverity": "MEDIUM",
          "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N",
          "integrityImpact": "HIGH",
          "userInteraction": "NONE",
          "attackComplexity": "LOW",
          "availabilityImpact": "NONE",
          "privilegesRequired": "LOW",
          "confidentialityImpact": "NONE"
        },
        "impactScore": 3.6,
        "exploitabilityScore": 1.8
      },
      {
        "type": "Primary",
        "source": "nvd@nist.gov",
        "cvssData": {
          "scope": "UNCHANGED",
          "version": "3.1",
          "baseScore": 5.5,
          "attackVector": "LOCAL",
          "baseSeverity": "MEDIUM",
          "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N",
          "integrityImpact": "HIGH",
          "userInteraction": "NONE",
          "attackComplexity": "LOW",
          "availabilityImpact": "NONE",
          "privilegesRequired": "LOW",
          "confidentialityImpact": "NONE"
        },
        "impactScore": 3.6,
        "exploitabilityScore": 1.8
      }
    ]
  },
  "affected": [
    {
      "source": "security-advisories@github.com",
      "affectedData": [
        {
          "vendor": "sigstore",
          "product": "cosign",
          "versions": [
            {
              "status": "affected",
              "version": "< 3.0.4"
            },
            {
              "status": "affected",
              "version": "< 2.6.2"
            }
          ]
        }
      ]
    }
  ],
  "published": "2026-01-10T07:16:03.030",
  "references": [
    {
      "url": "https://github.com/sigstore/cosign/commit/6832fba4928c1ad69400235bbc41212de5006176",
      "tags": [
        "Patch"
      ],
      "source": "security-advisories@github.com"
    },
    {
      "url": "https://github.com/sigstore/cosign/pull/4623",
      "tags": [
        "Issue Tracking"
      ],
      "source": "security-advisories@github.com"
    },
    {
      "url": "https://github.com/sigstore/cosign/security/advisories/GHSA-whqx-f9j3-ch6m",
      "tags": [
        "Exploit",
        "Vendor Advisory"
      ],
      "source": "security-advisories@github.com"
    }
  ],
  "vulnStatus": "Analyzed",
  "weaknesses": [
    {
      "type": "Secondary",
      "source": "security-advisories@github.com",
      "description": [
        {
          "lang": "en",
          "value": "CWE-345"
        }
      ]
    }
  ],
  "descriptions": [
    {
      "lang": "en",
      "value": "Cosign provides code signing and transparency for containers and binaries. Prior to versions 2.6.2 and 3.0.4, Cosign bundle can be crafted to successfully verify an artifact even if the embedded Rekor entry does not reference the artifact's digest, signature or public key. When verifying a Rekor entry, Cosign verifies the Rekor entry signature, and also compares the artifact's digest, the user's public key from either a Fulcio certificate or provided by the user, and the artifact signature to the Rekor entry contents. Without these comparisons, Cosign would accept any response from Rekor as valid. A malicious actor that has compromised a user's identity or signing key could construct a valid Cosign bundle by including any arbitrary Rekor entry, thus preventing the user from being able to audit the signing event. This issue has been patched in versions 2.6.2 and 3.0.4."
    },
    {
      "lang": "es",
      "value": "Cosign proporciona firma de código y transparencia para contenedores y binarios. Antes de las versiones 2.6.2 y 3.0.4, un paquete de Cosign podía ser manipulado para verificar con éxito un artefacto incluso si la entrada de Rekor incrustada no hacía referencia al *digest* del artefacto, a la firma o a la clave pública. Al verificar una entrada de Rekor, Cosign verifica la firma de la entrada de Rekor y también compara el *digest* del artefacto, la clave pública del usuario (ya sea de un certificado de Fulcio o proporcionada por el usuario) y la firma del artefacto con el contenido de la entrada de Rekor. Sin estas comparaciones, Cosign aceptaría cualquier respuesta de Rekor como válida. Un actor malicioso que haya comprometido la identidad o la clave de firma de un usuario podría construir un paquete de Cosign válido incluyendo cualquier entrada de Rekor arbitraria, impidiendo así al usuario auditar el evento de firma. Este problema ha sido parcheado en las versiones 2.6.2 y 3.0.4."
    }
  ],
  "lastModified": "2026-06-17T10:20:15.880",
  "configurations": [
    {
      "nodes": [
        {
          "negate": false,
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:sigstore:cosign:*:*:*:*:*:*:*:*",
              "vulnerable": true,
              "matchCriteriaId": "7ABA7B55-66EA-4E85-9F5E-1C392C4FCB6C",
              "versionEndExcluding": "2.6.2"
            },
            {
              "criteria": "cpe:2.3:a:sigstore:cosign:*:*:*:*:*:*:*:*",
              "vulnerable": true,
              "matchCriteriaId": "35768783-8EF1-41DB-8DD1-6870B46B647C",
              "versionEndExcluding": "3.0.4",
              "versionStartIncluding": "3.0.0"
            }
          ],
          "operator": "OR"
        }
      ]
    }
  ],
  "sourceIdentifier": "security-advisories@github.com"
}