Advisory

GHSA-fcv2-xgw5-pqxf

Also known as: CVE-2026-24137, GO-2026-4358

Summary

sigstore legacy TUF client allows for arbitrary file writes with target cache path traversal

Details

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.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-01-22 20:28 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

github.com/sigstore/sigstore

Go · All systems

Affected

  • introduced 0, fixed 1.10.4 (semver)

Fixed versions

1.10.4

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences