sigstore sigstore-go up to 1.10.3 pkg/tuf/client.go path traversal

Summaryinfo

A vulnerability was found in sigstore sigstore-go up to 1.10.3. It has been declared as critical. This vulnerability affects unknown code of the file pkg/tuf/client.go. Such manipulation leads to path traversal. This vulnerability is listed as CVE-2026-24137. The attack may be performed from remote. There is no available exploit. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in sigstore sigstore-go up to 1.10.3. Affected by this issue is some unknown processing of the file pkg/tuf/client.go. The manipulation with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Impacted is integrity, and availability. CVE summarizes:

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.

The advisory is shared for download at github.com. This vulnerability is handled as CVE-2026-24137 since 01/21/2026. The exploitation is known to be difficult. The attack may be launched remotely. Additional levels of successful authentication are necessary for exploitation. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1006.

The vulnerability scanner Nessus provides a plugin with the ID 296929 (Linux Distros Unpatched Vulnerability : CVE-2026-24137), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 1.10.4 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 8ec410a2993ea78083aecf0e473a85453039496e is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (296929) and EUVD (EUVD-2026-3781). VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Vendor

• sigstore

Name

• sigstore-go

Version

• 1.10.0
• 1.10.1
• 1.10.2
• 1.10.3

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion