CVE-2026-24137

Aliases:GHSA-fcv2-xgw5-pqxfGO-2026-4358
Deferred
Published: 23 Jan 2026, 00:04
Last modified:23 Jan 2026, 19:55

Vulnerability Summary

Overall Risk (default)
low
23/100
CVSS Score
5.8 MEDIUM
v3.1 (cve.org)
EPSS Score
0.02% LOW
0% probability 0.00%
KEV
Not listed
Ransomware
No reports
Public exploits
None found
Dark Web
Not detected

Timeline

23 Jan 2026, 00:04
Published
Vulnerability first disclosed
23 Jan 2026, 19:55
Last Modified
Vulnerability information updated

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.

CVSS Metrics

  • v3.1MEDIUMScore: 5.8CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N

EPSS Trends

Current EPSS score: 0.02% Percentile: 4%

Techniques & Countermeasures

  • CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

    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.

Affected Systems

  • github.com/sigstoresigstore

    < 1.10.4

  • sigstoresigstore

    < 1.10.4

References (6)