fix(auth): encode client-id in oauth requests#2383
Merged
Conversation
ensure client-id is encoded when passed to URL creation for oauth related requests
@supabase/auth-js
@supabase/functions-js
@supabase/postgrest-js
@supabase/realtime-js
@supabase/storage-js
@supabase/supabase-js
commit: |
mandarini
approved these changes
May 20, 2026
This was referenced May 20, 2026
This was referenced May 20, 2026
This was referenced May 20, 2026
This was referenced May 20, 2026
This was referenced May 20, 2026
mandarini
pushed a commit
to supabase/ssr
that referenced
this pull request
May 20, 2026
This PR updates `@supabase/supabase-js` to v2.106.1. **Source**: supabase-js-stable-release --- ## Release Notes ## v2.106.1 ## 2.106.1 (2026-05-20) ### 🩹 Fixes - **auth:** encode client-id in oauth requests ([#2383](supabase/supabase-js#2383)) - **misc:** hide dynamic import from hermesc ([#2381](supabase/supabase-js#2381)) ### ❤️ Thank You - Etienne Stalmans @staaldraad - Katerina Skroumpelou @mandarini This PR was created automatically. Co-authored-by: supabase-workflow-trigger[bot] <266661614+supabase-workflow-trigger[bot]@users.noreply.github.com>
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.
🔍 Description
ensure client-id is encoded when passed to URL creation for oauth related requests
What changed?
The client-id is url encoded before use in forming oauth requests
Why was this change needed?
client-id can contain URL influencing characters that are not escaped. If this is passed in an admin context, where the SDK is treated as a security boundary, there can be unintended side effects.
🔄 Breaking changes
📋 Checklist
<type>(<scope>): <description>pnpm nx formatto ensure consistent code formatting📝 Additional notes