fix(oauth): bind token exchanges to the original client request (#37704)#37740
Merged
Conversation
Zettat123
approved these changes
May 17, 2026
bircni
approved these changes
May 17, 2026
Member
|
@lunny checks fail |
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.
Backport #37704
This PR hardens OAuth token exchange validation by binding exchanged credentials to the client and redirect URI that originally obtained them.
What it changes:
redirect_uriin the token request differs from theredirect_uristored with the authorization codeWhy:
OAuth authorization codes and refresh tokens must remain bound to the client context that originally received them. Without those checks: