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…
Historical advisory saved 7 Nov 2026 06:38:30 UTC. The publisher may have updated it since then. Latest advisory.
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 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
- 7 Nov 2026 06:38:30 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