FKIE_CVE-2026-24137

Vulnerability from fkie_nvd - Published: 2026-01-23 00:15 - Updated: 2026-01-26 15:04
Severity ?
5.8 (Medium) - CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N
Summary
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.
References
security-advisories@github.comhttps://github.com/sigstore/sigstore/commit/8ec410a2993ea78083aecf0e473a85453039496e
security-advisories@github.comhttps://github.com/sigstore/sigstore/releases/tag/v1.10.4
security-advisories@github.comhttps://github.com/sigstore/sigstore/security/advisories/GHSA-fcv2-xgw5-pqxf
Impacted products
Vendor Product Version
To clipboard 

{
  "cveTags": [],
  "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\u00eda go com\u00fan 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\u00e9 de archivos objetivo en disco. Construye una ruta del sistema de archivos uniendo un directorio base de cach\u00e9 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\u00e9. 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\u00eda afectar a los clientes que est\u00e1n utilizando directamente el cliente TUF en sigstore/sigstore o est\u00e1n utilizando una versi\u00f3n anterior de Cosign. Los usuarios de implementaciones p\u00fablicas de Sigstore no se ven afectados, ya que los metadatos de TUF son validados por un qu\u00f3rum de colaboradores de confianza. Este problema ha sido solucionado en la versi\u00f3n 1.10.4. Como soluci\u00f3n alternativa, los usuarios pueden deshabilitar el almacenamiento en cach\u00e9 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 \u00faltima versi\u00f3n de sigstore/sigstore."
    }
  ],
  "id": "CVE-2026-24137",
  "lastModified": "2026-01-26T15:04:14.850",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "HIGH",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 5.8,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "NONE",
          "integrityImpact": "HIGH",
          "privilegesRequired": "HIGH",
          "scope": "CHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 1.3,
        "impactScore": 4.0,
        "source": "security-advisories@github.com",
        "type": "Secondary"
      }
    ]
  },
  "published": "2026-01-23T00:15:52.553",
  "references": [
    {
      "source": "security-advisories@github.com",
      "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"
    }
  ],
  "sourceIdentifier": "security-advisories@github.com",
  "vulnStatus": "Awaiting Analysis",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-22"
        }
      ],
      "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.