CVE-2026-24137: Github.com/sigstore/sigstore Path Traversal Vulnerability
MODERATECVE-2026-24137 is a MODERATE (CVSS 5.8) path traversal vulnerability (CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')) affecting Github.com/sigstore/sigstore libraries in the Go ecosystem. The issue involves sigstore legacy tuf client allows for arbitrary file writes with target cache path traversal. Remediation is available by upgrading affected packages to version 1.10.4.
CVE-2026-24137 at a Glance
Security Impact
CVSS: 5.8
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N).
How to Fix CVE-2026-24137
To remediate this vulnerability, upgrade all affected Github.com/sigstore/sigstore dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/sigstore/sigstore to 1.10.4Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/sigstore/sigstoreHow to Check if You Are Affected
To determine whether your application is affected by CVE-2026-24137, inspect your project dependencies for Github.com/sigstore/sigstore:
inspect dependencies for github.com/sigstore/sigstoreAnalyze the terminal output to locate any version of Github.com/sigstore/sigstore in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.10.4), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), where 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. In Github.com/sigstore/sigstore, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-24137 Affected Github.com/sigstore/sigstore Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/sigstore/sigstore
|
Go |
< 1.10.4
|
1.10.4
|
References
Frequently Asked Questions
What is CVE-2026-24137?
Which Github.com/sigstore/sigstore versions are affected?
What version fixes CVE-2026-24137?
Is github.com/sigstore/sigstore affected?
What is the CVSS score of CVE-2026-24137?
What CWE is associated with CVE-2026-24137?
How can I check Go dependencies for CVE-2026-24137?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-fcv2-xgw5-pqxf",
"modified" : "2026-02-27T21:37:24Z",
"published" : "2026-01-22T20:28:56Z",
"aliases" : [ "CVE-2026-24137" ],
"summary" : "sigstore legacy TUF client allows for arbitrary file writes with target cache path traversal",
"details" : "## Summary\n\nThe 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.\n\nNote 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.\n\nNote that this does not affect users of the public Sigstore deployment, where TUF metadata is validated by a quorum of trusted collaborators. \n\n## Impact\n\nA malicious TUF repository can trigger arbitrary file overwriting, limited to the permissions that the calling process has.\n\n## Workarounds\n\nUsers 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.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/sigstore/sigstore"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1.10.4"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 1.10.3"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/sigstore/sigstore/security/advisories/GHSA-fcv2-xgw5-pqxf"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-24137"
}, {
"type" : "WEB",
"url" : "https://github.com/sigstore/sigstore/commit/8ec410a2993ea78083aecf0e473a85453039496e"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/sigstore/sigstore"
}, {
"type" : "WEB",
"url" : "https://github.com/sigstore/sigstore/releases/tag/v1.10.4"
}, {
"type" : "WEB",
"url" : "https://pkg.go.dev/vuln/GO-2026-4358"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-22" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-01-22T20:28:56Z",
"nvd_published_at" : "2026-01-23T00:15:52Z"
}
}