CVE-2026-24137

{
  "id": "CVE-2026-24137",
  "cveTags": [],
  "metrics": {
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2026-24137",
          "role": "CISA Coordinator",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "no"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "version": "2.0.3",
          "timestamp": "2026-01-23T19:55:31.439546Z"
        }
      }
    ],
    "cvssMetricV31": [
      {
        "type": "Secondary",
        "source": "security-advisories@github.com",
        "cvssData": {
          "scope": "CHANGED",
          "version": "3.1",
          "baseScore": 5.8,
          "attackVector": "NETWORK",
          "baseSeverity": "MEDIUM",
          "vectorString": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N",
          "integrityImpact": "HIGH",
          "userInteraction": "NONE",
          "attackComplexity": "HIGH",
          "availabilityImpact": "NONE",
          "privilegesRequired": "HIGH",
          "confidentialityImpact": "NONE"
        },
        "impactScore": 4,
        "exploitabilityScore": 1.3
      }
    ]
  },
  "affected": [
    {
      "source": "security-advisories@github.com",
      "affectedData": [
        {
          "vendor": "sigstore",
          "product": "sigstore",
          "versions": [
            {
              "status": "affected",
              "version": "< 1.10.4"
            }
          ]
        }
      ]
    }
  ],
  "published": "2026-01-23T00:15:52.553",
  "references": [
    {
      "url": "https://github.com/sigstore/sigstore/commit/8ec410a2993ea78083aecf0e473a85453039496e",
      "source": "security-advisories@github.com"
    },
    {
      "url": "https://github.com/sigstore/sigstore/releases/tag/v1.10.4",
      "source": "security-advisories@github.com"
    },
    {
      "url": "https://github.com/sigstore/sigstore/security/advisories/GHSA-fcv2-xgw5-pqxf",
      "source": "security-advisories@github.com"
    }
  ],
  "vulnStatus": "Deferred",
  "weaknesses": [
    {
      "type": "Secondary",
      "source": "security-advisories@github.com",
      "description": [
        {
          "lang": "en",
          "value": "CWE-22"
        }
      ]
    }
  ],
  "descriptions": [
    {
      "lang": "en",
      "value": "sigstore framework is a common go library shared across sigstore services and clients. In versions 1.10.3 and below, the legacy TUF client (pkg/tuf/client.go) supports caching target files to disk. It constructs a filesystem path by joining a cache base directory with a target name sourced from signed target metadata; however, it does not validate that the resulting path stays within the cache base directory. A malicious TUF repository can trigger arbitrary file overwriting, limited to the permissions that the calling process has. Note that this should only affect clients that are directly using the TUF client in sigstore/sigstore or are using an older version of Cosign. Public Sigstore deployment users are unaffected, as TUF metadata is validated by a quorum of trusted collaborators. This issue has been fixed in version 1.10.4. As a workaround, users can disable disk caching for the legacy client by setting SIGSTORE_NO_CACHE=true in the environment, migrate to https://github.com/sigstore/sigstore-go/tree/main/pkg/tuf, or upgrade to the latest sigstore/sigstore release."
    },
    {
      "lang": "es",
      "value": "El framework sigstore es una librería go común compartida entre los servicios y clientes de sigstore. En las versiones 1.10.3 e inferiores, el cliente TUF heredado (pkg/tuf/client.go) admite el almacenamiento en caché de archivos objetivo en disco. Construye una ruta del sistema de archivos uniendo un directorio base de caché con un nombre de objetivo obtenido de metadatos de objetivo firmados; sin embargo, no valida que la ruta resultante permanezca dentro del directorio base de caché. Un repositorio TUF malicioso puede desencadenar la sobrescritura arbitraria de archivos, limitada a los permisos que tiene el proceso que realiza la llamada. Tenga en cuenta que esto solo debería afectar a los clientes que están utilizando directamente el cliente TUF en sigstore/sigstore o están utilizando una versión anterior de Cosign. Los usuarios de implementaciones públicas de Sigstore no se ven afectados, ya que los metadatos de TUF son validados por un quórum de colaboradores de confianza. Este problema ha sido solucionado en la versión 1.10.4. Como solución alternativa, los usuarios pueden deshabilitar el almacenamiento en caché en disco para el cliente heredado configurando SIGSTORE_NO_CACHE=true en el entorno, migrar a https://github.com/sigstore/sigstore-go/tree/main/pkg/tuf, o actualizar a la última versión de sigstore/sigstore."
    }
  ],
  "lastModified": "2026-06-17T10:22:41.597",
  "sourceIdentifier": "security-advisories@github.com"
}