sigstore legacy TUF client allows for arbitrary file writes with target cache path traversal
cve-program · CVE-2026-24137
Publishedsigstore 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.
Read the publisher's advisoryeuvd · EUVD-2026-3781
Publishedsigstore 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.
Read the publisher's advisorynvd · CVE-2026-24137
Publishedsigstore 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.
Read the publisher's advisoryosv · GHSA-fcv2-xgw5-pqxf
Published## Summary The legacy TUF client `pkg/tuf/client.go`, which supports caching target files to disk, constructs a filesystem path by joining a cache base directory with a target name sourced from signed target metadata, but it does not validate that the resulting path stays within the cache base directory. 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. As this TUF client implementation is deprecated, users should migrate to https://github.com/sigstore/sigstore-go/tree/main/pkg/tuf as soon as possible. Note that this does not affect users of the public Sigstore deployment, where TUF metadata is validated by a quorum of trusted collaborators. ## Impact A malicious TUF repository can trigger arbitrary file overwriting, limited to the permissions that the calling process has. ## Workarounds 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.
Read the publisher's advisoryosv · GO-2026-4358
PublishedSigstore legacy TUF client allows for arbitrary file writes with target cache path traversal in github.com/sigstore/sigstore
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-24137 · CVE overview and exploitation status
cve-program · CVE-2026-24137
- https://github.com/sigstore/sigstore/security/advisories/GHSA-fcv2-xgw5-pqxf
- https://github.com/sigstore/sigstore/commit/8ec410a2993ea78083aecf0e473a85453039496e
- https://github.com/sigstore/sigstore/releases/tag/v1.10.4
euvd · EUVD-2026-3781
- https://github.com/sigstore/sigstore/security/advisories/GHSA-fcv2-xgw5-pqxf
- https://github.com/sigstore/sigstore/commit/8ec410a2993ea78083aecf0e473a85453039496e
- https://github.com/sigstore/sigstore/releases/tag/v1.10.4
nvd · CVE-2026-24137
- https://github.com/sigstore/sigstore/commit/8ec410a2993ea78083aecf0e473a85453039496e
- https://github.com/sigstore/sigstore/releases/tag/v1.10.4
- https://github.com/sigstore/sigstore/security/advisories/GHSA-fcv2-xgw5-pqxf
osv · GHSA-fcv2-xgw5-pqxf
- https://github.com/sigstore/sigstore/security/advisories/GHSA-fcv2-xgw5-pqxf
- https://nvd.nist.gov/vuln/detail/CVE-2026-24137
- https://github.com/sigstore/sigstore/commit/8ec410a2993ea78083aecf0e473a85453039496e
- https://github.com/sigstore/sigstore
- https://github.com/sigstore/sigstore/releases/tag/v1.10.4
- https://pkg.go.dev/vuln/GO-2026-4358
osv · GO-2026-4358
Related changes
Linked by CVE identifierNo related changes are available here.