Skip to content

Fix GO-2026-4762: upgrade grpc to v1.79.3#4138

Merged
reinkrul merged 2 commits intoV5.4from
V5_4/fix-grpc-go-2026-4762
Mar 31, 2026
Merged

Fix GO-2026-4762: upgrade grpc to v1.79.3#4138
reinkrul merged 2 commits intoV5.4from
V5_4/fix-grpc-go-2026-4762

Conversation

@reinkrul
Copy link
Copy Markdown
Member

@reinkrul reinkrul commented Mar 31, 2026

Summary

  • Upgrades google.golang.org/grpc from v1.64.1 to v1.79.3 to fix GO-2026-4762
  • This vulnerability allows authorization bypass via a missing leading slash in the :path header in gRPC-Go
  • The affected call site is network/transport/grpc/connection_manager.go:229 (grpc.Server.Serve)

Test plan

  • CI passes (build + unit tests)
  • Verify govulncheck no longer reports GO-2026-4762

🤖 Generated with Claude Code

reinkrul and others added 2 commits March 31, 2026 08:46
Fixes authorization bypass vulnerability in gRPC-Go via missing leading
slash in :path header (GO-2026-4762).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@qltysh
Copy link
Copy Markdown

qltysh bot commented Mar 31, 2026

Qlty

Coverage Impact

This PR will not change total coverage.

🚦 See full report on Qlty Cloud »

🛟 Help
  • Diff Coverage: Coverage for added or modified lines of code (excludes deleted files). Learn more.

  • Total Coverage: Coverage for the whole repository, calculated as the sum of all File Coverage. Learn more.

  • File Coverage: Covered Lines divided by Covered Lines plus Missed Lines. (Excludes non-executable lines including blank lines and comments.)

    • Indirect Changes: Changes to File Coverage for files that were not modified in this PR. Learn more.

@reinkrul reinkrul merged commit a5c362a into V5.4 Mar 31, 2026
8 checks passed
@reinkrul reinkrul deleted the V5_4/fix-grpc-go-2026-4762 branch March 31, 2026 10:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants