DEBIAN-CVE-2026-24137

Advisory lineage Upstream: 1 Downstream: 0
Upstream
CVE-2026-24137
Published: 23 Jan 2026, 00:15
Last modified:28 Apr 2026, 20:31

Vulnerability Summary

Overall Risk (default)
low
23/100
CVSS Score
5.8 MEDIUM
3.1 (osv_debian)
EPSS Score
No data
KEV
Not listed
Ransomware
No reports
Public exploits
None found
Dark Web
Not detected

Timeline

23 Jan 2026, 00:15
Published
Vulnerability first disclosed
28 Apr 2026, 20:31
Last Modified
Vulnerability information updated

Description

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.

CVSS Metrics

  • v3.1•MEDIUM•Score: 5.8CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N

Affected Systems

  • debian•golang-github-sigstore-sigstore

    all | all | < 1.10.4-1

References (1)