CVE-2026-33175High· 8.8▾ TwilightAuth0OAuthenticator has an Authentication Bypass via Unverified Email Claims
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 48.4 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Jul 13.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
0.4%
Last analysed / modified upstream
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.
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.
email_verified field in an Authenticator.post_auth_hook functionemail as the username claimoauthenticator < 17.4.0Upgrade to a patched release:
oauthenticator 17.4.0Connected by shared product, vendor, weakness, or advisory.
CVE-2024-37300High· 8.1Globus `identity_provider` restriction ignored when used with `allow_all` in JupyterHub 5.0
CVE-2024-29033High· 7.5GoogleOAuthenticator.hosted_domain incorrectly verifies membership of an Google organization/workspace
CVE-2020-26250Medium· 6.3Base class whitelist configuration ignored in OAuthenticator