oauthenticator
Affected
- introduced
0, fixed17.4.0(ecosystem)
Fixed versions
17.4.0
Fix
- Fixed version
17.4.0pip install --upgrade oauthenticator==17.4.0
Advisory
Also known as: CVE-2026-33175, PYSEC-2026-2238
Auth0OAuthenticator has an Authentication Bypass via Unverified Email Claims
Summary
An authentication bypass vulnerability in oauthenticator allows an attacker with an unverified email address on an Auth0 tenant to login to JupyterHub. When email is used as the usrname_claim, this gives users control over their username and the possibility of account takeover.
Impact
This is an Authentication Bypass Vulnerability. Any Auth0 tenant leveraging the Auth0OAuthenticator mapping the email claim to the JupyterHub username is impacted. By default, Auth0 handles email verification as a user flag, not a hard block to authentication streams. If an attacker can register an account with the Auth0 tenant with an unverified email and knows the email of an existing user on the system, they can authenticate as that user.
Patches
Workarounds
email_verified field in an Authenticator.post_auth_hook functionemail as the username claimHigh Basis: The source's own band: HIGH
0, fixed 17.4.0 (ecosystem)17.4.0
17.4.0pip install --upgrade oauthenticator==17.4.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0