GitHub Advisoryadvisory · PyPI

GHSA-rrvg-cxh4-qhrv Auth0OAuthenticator has an Authentication Bypass via Unverified Email Claims

HIGH Published 2026-04-03 Modified 2026-04-06 Official page ↗
Aliases
CVE-2026-33175
Ecosystem
PyPI
Packages
oauthenticator
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weaknesses
CWE-287, CWE-290
Reviewed
2026-04-03

Affected packages

• PyPI oauthenticator: < 17.4.0 → fixed in 17.4.0

Description

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 • Upgrade oauthenticator to 17.4 Workarounds • Check `email_verified` field in an `Authenticator.post_auth_hook` function • Do not use `email` as the username claim • Enforce email verification in auth0

Related

Alias · CVE (1)

  • CVE-2026-33175 OAuthenticator is software that allows OAuth2 identity providers to be plugged in and used with JupyterHub. vulnerability

Weakness · CWE (2)

  • CWE-287 Improper Authentication weakness
  • CWE-290 Authentication Bypass by Spoofing weakness

References