CVE-2026-24137: sigstore legacy TUF client allows for arbitrary file writes with target cache path traversal
(updated )
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.
References
- github.com/advisories/GHSA-fcv2-xgw5-pqxf
- github.com/sigstore/sigstore
- github.com/sigstore/sigstore/commit/8ec410a2993ea78083aecf0e473a85453039496e
- github.com/sigstore/sigstore/releases/tag/v1.10.4
- github.com/sigstore/sigstore/security/advisories/GHSA-fcv2-xgw5-pqxf
- nvd.nist.gov/vuln/detail/CVE-2026-24137
Code Behaviors & Features
Detect and mitigate CVE-2026-24137 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →