Update module github.com/sigstore/sigstore to v1.10.4 [SECURITY] (main)#3087
Merged
renovate[bot] merged 1 commit intomainfrom Feb 13, 2026
Merged
Conversation
renovate
bot
force-pushed
the
renovate/main-go-github.com-sigstore-sigstore-vulnerability
branch
from
33f05fe to
c2e44e6
Compare
renovate
bot
force-pushed
the
renovate/main-go-github.com-sigstore-sigstore-vulnerability
branch
from
c2e44e6 to
e31bc0c
Compare
renovate
bot
force-pushed
the
renovate/main-go-github.com-sigstore-sigstore-vulnerability
branch
3 times, most recently
from
155a574 to
b14bac7
Compare
renovate
bot
force-pushed
the
renovate/main-go-github.com-sigstore-sigstore-vulnerability
branch
from
b14bac7 to
3d483de
Compare
renovate
bot
deleted the
renovate/main-go-github.com-sigstore-sigstore-vulnerability
branch
Codecov Report✅ All modified and coverable lines are covered by tests.
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.10.3→v1.10.4GitHub Vulnerability Alerts
CVE-2026-24137
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=truein the environment, migrate to https://github.com/sigstore/sigstore-go/tree/main/pkg/tuf, or upgrade to the latest sigstore/sigstore release.Release Notes
sigstore/sigstore (github.com/sigstore/sigstore)
v1.10.4Compare Source
What's Changed
Full Changelog: sigstore/sigstore@v1.10.3...v1.10.4
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.