fix(cve): CVE-2026-33186 - bump google.golang.org/grpc v1.63.2 → v1.79.3#983
Merged
divyansh42 merged 1 commit intoJun 2, 2026
Conversation
- Update google.golang.org/grpc from v1.63.2 to v1.79.3 - Addresses authorization bypass via missing leading slash in :path pseudo-header (GHSA-p77j-4mvh-x3m3) - go mod tidy/verify/vendor all pass; 5 packages tested OK Resolves: SRVKP-11972 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
infernus01
approved these changes
Jun 1, 2026
|
@infernus01: changing LGTM is restricted to collaborators DetailsIn response to this: Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: divyansh42, infernus01 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
divyansh42
deleted the
fix/SRVKP-11972-cve-2026-33186-grpc-release-v0.2.2-attempt-1
branch
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
2 participants
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.
CVE Details
:pathpseudo-header. gRPC-Go servers accepted requests where:pathomitted the mandatory leading slash, causing authorization interceptors (includinggrpc/authz) to evaluate the raw non-canonical path and miss "deny" rules, allowing bypass when a fallback "allow" rule was present.google.golang.org/grpc< v1.79.3Fix Summary
google.golang.org/grpcfromv1.63.2→v1.79.3go mod tidygo mod tidy && go mod verify && go mod vendor— all passed ✅Test Results
✅ Tests passed — Go tests passed (5 package(s) OK).
Command:
go test ./...Breaking Changes
None expected. The fix rejects requests with a non-canonical
:path(no leading slash) withcodes.Unimplemented— these were malformed requests that should never have been accepted. Legitimate clients always send a leading slash.Jira References
SRVKP-11972
Verification Steps
google.golang.org/grpcis atv1.79.3ingo.modvendor/is consistent withgo.sum(go mod verify)Risk Assessment
Low — grpc v1.79.3 is a security patch release. The behavioral change (rejecting malformed
:pathheaders) only affects clients sending non-standard requests. All standard gRPC clients are unaffected.Co-Authored-By: Claude Sonnet 4.6 noreply@anthropic.com