Skip to content

Tighten Supabase service role key match, add Auth0 patterns - #154

Merged
asamassekou10 merged 2 commits into
asamassekou10:mainfrom
AlvaroBalbin:fix-issue-56
Aug 19, 2026
Merged

asamassekou10 merged 2 commits into
asamassekou10:mainfrom
AlvaroBalbin:fix-issue-56

Conversation

@AlvaroBalbin

Copy link
Copy Markdown
Contributor

The Supabase service role key pattern matched any HS256 JWT header, so it also flagged public anon keys since both share the same header. I scoped the match to require the base64-encoded service_role claim in the payload, the same technique already used in cli/hooks/patterns.js, and bumped severity to critical now that the match is precise. I also added dedicated patterns for Auth0 client secret assignments and Auth0 Management API tokens, which previously were only caught when paired with a client_secret on the same line as the tenant domain. Fixes #56.

Ran this through the project's own CI on my fork before opening it, all green.

@asamassekou10
asamassekou10 merged commit e1b1b09 into asamassekou10:main Aug 19, 2026
4 checks passed
@asamassekou10

Copy link
Copy Markdown
Owner

Thanks for the contribution, Alvaro. I kept your original fix and added a separate follow-up for the JWT claim-order edge cases and hook coverage. All checks are passing, and the PR is now merged.

@asamassekou10 asamassekou10 mentioned this pull request Aug 19, 2026
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.

Improve Supabase and Auth0 secret patterns

2 participants