-
Notifications
You must be signed in to change notification settings - Fork 46
Update module github.com/sigstore/sigstore to v1.10.4 [SECURITY] (release-v0.7) #3089
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: release-v0.7
Are you sure you want to change the base?
Update module github.com/sigstore/sigstore to v1.10.4 [SECURITY] (release-v0.7) #3089
Conversation
ℹ️ Artifact update noticeFile name: acceptance/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
File name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
CI Feedback 🧐A test triggered by this PR failed. Here is an AI-generated analysis of the failure:
|
5a5bd11 to
abd9c4d
Compare
abd9c4d to
3cfb835
Compare
This PR contains the following updates:
v1.9.1→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
v1.10.3Compare Source
What's Changed
v1.10.3 adds
ValidatePubKeyback to thecryptoutilspackage to avoid a breaking API change.Full Changelog: sigstore/sigstore@v1.10.2...v1.10.3
v1.10.2v1.10.2
Functionally equivalent to v1.10.0. v1.10.1 has been retracted to remove copied code.
v1.10.0
Breaking change
#2194 moves
cryptoutils.ValidatePubKeytogoodkey.ValidatePubKeyto minimize the dependency tree for clients using the cryptoutils package.Features
Refactoring
v1.10.0Compare Source
Breaking change
#2194 moves
cryptoutils.ValidatePubKeytogoodkey.ValidatePubKeyto minimize the dependency tree for clients using thecryptoutilspackage.Features
Refactoring
Full Changelog: sigstore/sigstore@v1.9.5...v1.10.0
v1.9.5Compare Source
What's Changed
Full Changelog: sigstore/sigstore@v1.9.4...v1.9.5
v1.9.4Compare Source
What's Changed
Full Changelog: sigstore/sigstore@v1.9.3...v1.9.4
v1.9.3Compare Source
What's Changed
New Contributors
Full Changelog: sigstore/sigstore@v1.9.2...v1.9.3
v1.9.2Compare Source
What's Changed
New Contributors
Full Changelog: sigstore/sigstore@v1.9.1...v1.9.2
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.