chore: update to JWT v5 to fix vulnerability GO-2025-3553 #282
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.
This PR updates the JWT implementation to use v5 to fix the vulnerability GO-2025-3553 related to excessive memory allocation during header parsing.
Changes:
RegisteredClaims
which has the same fields asStandardClaims
jwt.ClaimStrings
for audience which is compatible with both string and array formatsAll tests are passing:
github.com/go-oauth2/oauth2/v4
: ✅github.com/go-oauth2/oauth2/v4/generates
: ✅github.com/go-oauth2/oauth2/v4/manage
: ✅github.com/go-oauth2/oauth2/v4/server
: ✅github.com/go-oauth2/oauth2/v4/store
: ✅