Bump golang-jwt, x/net, protobuf to clear Go-1.20-compatible CVEs#363
Merged
Conversation
Surfaced by OSV-Scanner against go.mod. These three bumps stay within
the existing `go 1.20` directive (each fixed version declares
`go 1.17`-`1.18` in its own go.mod) -- no Go-toolchain change needed.
golang-jwt/jwt/v5 5.2.1 -> 5.2.2
GO-2025-3553 / GHSA-mh63-6h87-95cp (HIGH 8.7)
Excess memory allocation in parseToken. Patched in the 5.2.x
branch; v5.3.0 forced `go 1.21` so we take the backport.
google.golang.org/protobuf 1.28.1 -> 1.33.0
GO-2024-2611 / GHSA-8r3f-844c-mc37 (HIGH 7.5)
Infinite-loop DoS in Unmarshal of arbitrary input. Fixed version
still declares `go 1.17`.
golang.org/x/net 0.21.0 -> 0.33.0
GO-2024-2687 / GHSA-4v7x-pqxf-cx7m (MED 5.3) - HTTP/2 CONTINUATION flood
GO-2024-3333 (LOW) - HTML tokenizer parse bug
Fixed version still declares `go 1.18`. Stopping at v0.33.0
because v0.36.0+ forces `go 1.23`; the remaining x/net advisories
will be cleared by a follow-up Go-toolchain bump.
Net OSV-Scanner result after this PR:
HIGH: 5 -> 3 (apache/thrift, x/crypto, x/oauth2 still need Go bump)
MED: 5 -> 4
LOW: 60 -> 59 (55 of the LOWs are stdlib@1.20.x advisories that
only clear when the build toolchain is upgraded)
Co-authored-by: Isaac
Signed-off-by: Vikrant Puppala <vikrant.puppala@databricks.com>
gopalldb
approved these changes
May 21, 2026
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.
Summary
Three dependency bumps surfaced by OSV-Scanner against
go.mod. All stay within the existinggo 1.20directive — each fixed version declaresgo 1.17/1.18in its owngo.mod, so no Go-toolchain change is forced by this PR.golang-jwt/jwt/v5google.golang.org/protobufgolang.org/x/netWhy these specific patch versions
jwt/v5.2.2is the backport of the fix;v5.3.0forcesgo 1.21.protobuf 1.33.0is the lowest patched version; declaresgo 1.17.x/net 0.33.0is the highestx/netwe can take while staying ongo 1.20—v0.36.0+forcesgo 1.23. The remaining 4x/netadvisories (GO-2025-3503,GO-2025-3595,GO-2026-4440/4441/4918) will be cleared by a follow-up Go-toolchain bump.Net OSV-Scanner result after this PR
Test plan
go build ./...cleango mod tidyno further changesgo 1.20directive ingo.modunchangedThis pull request was AI-assisted by Isaac.