chore(deps): bump github.com/sigstore/sigstore-go from 1.1.4 to 1.2.0#315
chore(deps): bump github.com/sigstore/sigstore-go from 1.1.4 to 1.2.0#315dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [github.com/sigstore/sigstore-go](https://github.com/sigstore/sigstore-go) from 1.1.4 to 1.2.0. - [Release notes](https://github.com/sigstore/sigstore-go/releases) - [Commits](sigstore/sigstore-go@v1.1.4...v1.2.0) --- updated-dependencies: - dependency-name: github.com/sigstore/sigstore-go dependency-version: 1.2.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Duplication | 0 |
AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.
TIP This summary will be updated as you push new changes.
There was a problem hiding this comment.
Pull Request Overview
While the project's quality metrics are reported as up to standards, significant security risks and verification gaps exist. High-severity vulnerabilities identified in the oras-go library and the pinned Go toolchain (CVE-2026-50162, CVE-2026-50151, CVE-2026-42505) pose threats of directory traversal, credential exposure, and information disclosure. These security flaws should be mitigated to ensure a secure build environment. Additionally, there is no evidence that compilation and integration tests have been executed to confirm compatibility with the updated library features and transitive dependencies. Documenting these tests is a necessary step to validate that the changes do not introduce regressions.
1 comment outside of the diff
go.mod
line 3🟡 MEDIUM RISK
The pinned Go toolchain version is affected by CVE-2026-42505, which involves a potential information disclosure vulnerability in thecrypto/tlspackage during Encrypted Client Hello (ECH) handshakes.
Test suggestions
- Verify successful project compilation and execution of existing integration tests to ensure no breaking changes from the library updates.
Prompt proposal for missing tests
Consider implementing these tests if applicable:
1. Verify successful project compilation and execution of existing integration tests to ensure no breaking changes from the library updates.
TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback
Bumps github.com/sigstore/sigstore-go from 1.1.4 to 1.2.0.
Release notes
Sourced from github.com/sigstore/sigstore-go's releases.
... (truncated)
Commits
8ca80c4Fix conformance test failures for managed-key verification (#561) (#638)40d743aBump the minor-patch group across 2 directories with 10 updates (#637)7960906Bump golangci/golangci-lint-action from 9.2.0 to 9.2.1 (#631)ef6e924Encode Rekor v2 DSSE envelopes as hashedrekord (#627)56c2528Verify Rekor v2 inclusion using reconstructed leaf hash (#635)dbb07e6Prevent multi-log threshold bypasses via single compromised log (#633)7e8ee0fbundle: cap raw TlogEntries length before per-entry parse (#630)58c7950Bump github.com/in-toto/in-toto-golang from 0.10.0 to 0.11.0 (#624)1ad51eaBump github.com/in-toto/in-toto-golang (#623)566ec6cBump sigstore/sigstore-conformance from 0.0.26 to 0.0.27 (#621)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.