Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

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

CVSS 3.1 5.8 MEDIUMEUVD CVSS 3.1 5.8 CVSS 3.1 · [email protected] · Secondary 5.8 MEDIUMCVSS_V3 Publisher rating MODERATEFixed by github.com/sigstore/sigstore 1.10.4osv · severity unknownFixed by github.com/sigstore/sigstore 1.10.4KEV status unknown

cve-program · CVE-2026-24137

Published

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.

Read the publisher's advisory

euvd · EUVD-2026-3781

Published

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.

Read the publisher's advisory

nvd · CVE-2026-24137

Published

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.

Read the publisher's advisory

osv · 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 advisory

osv · GO-2026-4358

Published

Sigstore legacy TUF client allows for arbitrary file writes with target cache path traversal in github.com/sigstore/sigstore

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-24137

Published

sigstore

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "sigstore",
                    "product": "sigstore",
                    "versions": [
                        {
                            "version": "< 1.10.4",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2026-3781

Published

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

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2026-24137

Published

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

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-fcv2-xgw5-pqxf

Published

github.com/sigstore/sigstore

Go

SEMVER · introduced 0 → fixed 1.10.4

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GO-2026-4358

Published

github.com/sigstore/sigstore

Go

SEMVER · introduced 0 → fixed 1.10.4

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 11:47 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current