Repository navigation
fix: upgrade extras/dagger grpc to v1.83.2 - #3422
Merged
Merged
Conversation
jiparis
approved these changes
Sep 9, 2026
jiparis
deleted the
chainloop/fix-ghsa-vp52-pcj8-j9qc-20260909-091840
branch
September 9, 2026 11:53
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.
Summary
Bump the auxiliary
extras/daggermodule fromgoogle.golang.org/grpcv1.82.1tov1.83.2to remove the vulnerable gRPC-Go release from that submodule. The assessment hint suggestedv1.83.1, but the current vulnerability database also flagsv1.83.1, so this remediation uses the next fixed release.Vulnerability Fixed
GHSA-vp52-pcj8-j9qc(HIGH): gRPC-Go heap memory exhaustion (OOM) via HTTP/2 DATA frame fragmentation.Changes Made
extras/dagger/go.modto requiregoogle.golang.org/grpc v1.83.2instead of the vulnerablev1.82.1.extras/dagger/go.sumwith the matching checksums forgoogle.golang.org/grpc v1.83.2.v1.83.2rather than the hintedv1.83.1because the current Grype database reports a separate high-severity gRPC advisory againstv1.83.1.Verification
Ran
syft dir:extras/dagger -o cyclonedx-json=/workspace/run/.scan/dagger-sbom-fixed.jsonfollowed byGRYPE_DB_AUTO_UPDATE=false grype sbom:/workspace/run/.scan/dagger-sbom-fixed.json --only-fixed -o json. Outcome:resolved. The scan no longer reportsGHSA-vp52-pcj8-j9qcforgoogle.golang.org/grpcinextras/daggerafter the bump tov1.83.2.Risk Assessment
View the risk assessment in Chainloop