CVE-2026-24137 Details
Description
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.
A path traversal vulnerability has been identified in the legacy TUF client of the Sigstore framework, specifically in versions through 1.10.3. The issue arises because the client caches target files to disk without properly validating that the file paths remain within the designated cache directory. This flaw can be exploited by a malicious TUF repository to overwrite arbitrary files, depending on the permissions of the process using the client. However, this vulnerability does not affect users of the public Sigstore deployment, where TUF metadata is safeguarded by a group of trusted collaborators.
Users can upgrade to Sigstore version 1.10.4, where this vulnerability has been patched. Alternatively, they can disable disk caching for the legacy TUF client by setting the environment variable SIGSTORE_NO_CACHE=true, or migrate to the updated TUF client available in the Sigstore Go repository.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Jan 23, 2026CISA-ADP
Assessed Jan 23, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/sigstore/sigstore/commit/8ec410a2993ea78083aecf0e473a85453039496e | [email protected] | Source CodeVendor |
| https://github.com/sigstore/sigstore/releases/tag/v1.10.4 | [email protected] | Release NotesVendor |
| https://github.com/sigstore/sigstore/security/advisories/GHSA-fcv2-xgw5-pqxf | [email protected] | AdvisoryRemedyVendor |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-22 | Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| sigstore | All versions |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Jan 23, 2026 | New CVE Received | [email protected] |
Volerion