sigstore legacy TUF client allows for arbitrary file writes with target cache path traversal
cve-program · CVE-2026-24137
Publishedsigstore 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.
Read the publisher's advisoryeuvd · EUVD-2026-3781
Publishedsigstore 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.
Read the publisher's advisorynvd · CVE-2026-24137
Publishedsigstore 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.
Read the publisher's advisoryosv · GHSA-fcv2-xgw5-pqxf
Published## Summary 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. ## Impact A malicious TUF repository can trigger arbitrary file overwriting, limited to the permissions that the calling process has. ## Workarounds 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.
Read the publisher's advisoryosv · GO-2026-4358
PublishedSigstore legacy TUF client allows for arbitrary file writes with target cache path traversal in github.com/sigstore/sigstore
Read the publisher's advisoryAffected versions, risk and source history
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
cve-program · CVE-2026-24137
Publishedsigstore legacy TUF client allows for arbitrary file writes with target cache path traversal
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.
- Source published
- 23 Jan 2026 00:04:19 UTC
- Source modified
- 23 Jan 2026 19:55:42 UTC
- Saved here
- 23 Oct 2026 15:48:27 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · 5.8 CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N
euvd · EUVD-2026-3781
Publishedsigstore 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…
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.
Additional publisher context
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Jan 23, 2026, 12:04:19 AM
dateUpdated: Jan 23, 2026, 7:55:42 PM
10 related source bulletins · separate from aliases
openSUSE-SU-2026:21481-1: Security update for vexctl
CVE-2024-45337 · CVE-2025-22868 · CVE-2025-22869 · CVE-2025-22870 · CVE-2025-27144 · CVE-2025-30204 · CVE-2025-58181 · CVE-2026-22772 · CVE-2026-24137
SUSE-SU-2026:0592-1: Security update for vexctl
CVE-2024-45337 · CVE-2025-22868 · CVE-2025-22869 · CVE-2025-22870 · CVE-2025-27144 · CVE-2025-30204 · CVE-2025-58181 · CVE-2026-22772 · CVE-2026-24137
openSUSE-SU-2026:10235-1: cosign-3.0.5-1.1 on GA media
CVE-2026-22772 · CVE-2026-23991 · CVE-2026-23992 · CVE-2026-24122 · CVE-2026-24137 · CVE-2026-26958
openSUSE-SU-2026:20730-1: Security update for apptainer
CVE-2023-45288 · CVE-2024-28180 · CVE-2024-3727 · CVE-2024-41110 · CVE-2024-45337 · CVE-2024-45338 · CVE-2025-22869 · CVE-2025-22870 · CVE-2025-22872 · CVE-2025-27144 · CVE-2025-47911 · CVE-2025-47913 · CVE-2025-47914 · CVE-2025-58181 · CVE-2025-58190 · CVE-2025-65105 · CVE-2025-8556 · CVE-2026-24137 · CVE-2026-33186 · CVE-2026-34986
openSUSE-SU-2026:10700-1: apptainer-1.4.5-4.1 on GA media
CVE-2026-24137 · CVE-2026-33186 · CVE-2026-34986
openSUSE-SU-2026:20386-1: Security update for cosign
CVE-2025-11065 · CVE-2025-58181 · CVE-2026-22703 · CVE-2026-22772 · CVE-2026-23991 · CVE-2026-23992 · CVE-2026-24122 · CVE-2026-24137 · CVE-2026-26958
openSUSE-SU-2026:10230-1: vexctl-0.4.1+git78.f951e3a-1.1 on GA media
CVE-2024-45337 · CVE-2025-22868 · CVE-2025-22869 · CVE-2025-22870 · CVE-2025-27144 · CVE-2025-30204 · CVE-2025-58181 · CVE-2026-22772 · CVE-2026-24137
SUSE-SU-2026:20904-1: Security update for cosign
CVE-2025-11065 · CVE-2025-58181 · CVE-2026-22703 · CVE-2026-22772 · CVE-2026-23991 · CVE-2026-23992 · CVE-2026-24122 · CVE-2026-24137 · CVE-2026-26958
SUSE-SU-2026:0777-1: Security update for cosign
CVE-2025-11065 · CVE-2025-58181 · CVE-2026-22703 · CVE-2026-22772 · CVE-2026-23991 · CVE-2026-23992 · CVE-2026-24122 · CVE-2026-24137 · CVE-2026-26958
SUSE-SU-2026:2609-1: Security update for apptainer
CVE-2026-24137 · CVE-2026-33186 · CVE-2026-33814 · CVE-2026-34986 · CVE-2026-39821 · CVE-2026-39827 · CVE-2026-39828 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39831 · CVE-2026-39832 · CVE-2026-39833 · CVE-2026-39834 · CVE-2026-39835 · CVE-2026-42508 · CVE-2026-46595 · CVE-2026-46597 · CVE-2026-46598 · CVE-2026-48785
- Source published
- Jan 23, 2026, 12:04:19 AM (timezone not stated)
- Source modified
- Jan 23, 2026, 7:55:42 PM (timezone not stated)
- Saved here
- 15 Nov 2026 09:31:19 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
EUVD CVSS 3.1 · 5.8 CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N
nvd · CVE-2026-24137
Publishedsigstore 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…
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.
Additional publisher context
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Deferred
Weakness classifications: CWE-22
Original publisher date fields
published: 2026-01-23T00:15:52.553
lastModified: 2026-06-17T10:22:41.597
- Source published
- 23 Jan 2026 00:15:52 UTC
- Source modified
- 17 Jun 2026 10:22:41 UTC
- Saved here
- 25 Oct 2026 06:17:10 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · [email protected] · Secondary · 5.8 CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N
osv · GHSA-fcv2-xgw5-pqxf
Publishedsigstore legacy TUF client allows for arbitrary file writes with target cache path traversal
## Summary 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. ## Impact A malicious TUF repository can trigger arbitrary file overwriting, limited to the permissions that the calling process has. ## Workarounds 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.
- Source published
- 22 Jan 2026 20:28:56 UTC
- Source modified
- 10 Sep 2026 03:50:32 UTC
- Saved here
- 24 Oct 2026 13:19:41 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V3 · CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N
Publisher rating · MODERATE
osv · GO-2026-4358
PublishedSigstore legacy TUF client allows for arbitrary file writes with target cache path traversal in github.com/sigstore/sigstore
Sigstore legacy TUF client allows for arbitrary file writes with target cache path traversal in github.com/sigstore/sigstore
- Source published
- 19 Feb 2026 17:28:55 UTC
- Source modified
- 25 Feb 2026 20:15:11 UTC
- Saved here
- 24 Oct 2026 13:19:41 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.