Vulnerabilities in pkg:pypi/oauthenticator

PACKAGE
Advisory Identifier: GHSA-rrvg-cxh4-qhrv
Advisory Summary

CVE-2026-33175 is a HIGH (CVSS 8.8) authentication bypass vulnerability (CWE-287: Improper Authentication) affecting Oauthenticator libraries in the PyPI ecosystem. The issue involves auth0oauthenticator has an authentication bypass via unverified email claims. Remediation is available by upgrading affected packages to version 17.4.0.

6 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:pypi/oauthenticator

6 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:pypi/oauthenticator. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-rrvg-cxh4-qhrv CVE-2026-33175 HIGH Auth0OAuthenticator has an Authentication Bypass via Unverified Email Claims
GHSA-8x3m-m3x9-54fj CVE-2018-7206 HIGH JupyterHub OAuthenticator elevation of privilege
GHSA-384w-5v3f-q499 CVE-2020-26250 HIGH Base class whitelist configuration ignored in OAuthenticator
GHSA-gprj-3p75-f996 CVE-2024-37300 HIGH Globus `identity_provider` restriction ignored when used with `allow_all` in JupyterHub 5.0
GHSA-55m3-44xf-hg4h CVE-2024-29033 HIGH GoogleOAuthenticator.hosted_domain incorrectly verifies membership of an Google organization/workspace
GHSA-r7v4-jwx9-wx43 CVE-2022-31027 MODERATE Authorization Bypass Through User-Controlled Key when using CILogonOAuthenticator oauthenticator

CVE-2026-33175 at a Glance

CVE Identifier CVE-2026-33175
GHSA Identifier GHSA-rrvg-cxh4-qhrv
Severity HIGH
CVSS v3.1 Base Score 8.8
CWE Classification CWE-287: Improper Authentication
Affected Product Oauthenticator
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 8.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-33175

To remediate this vulnerability, upgrade all affected Oauthenticator dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

oauthenticator fixed: 17.4.0
pip install oauthenticator>=17.4.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show oauthenticator

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-33175, inspect your installed packages using pip:

pip show oauthenticator

Analyze the terminal output to locate any version of Oauthenticator in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 17.4.0), your application is affected.

Note: The pip show oauthenticator command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-287: Improper Authentication, where when an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. In Oauthenticator, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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](https://support.auth0.com/center/s/article/Enforce-Email-Verification-With-Sending-Email-After-Each-Denied-Access)

CVE-2026-33175 Affected Oauthenticator Versions

1 component(s)
Fixed Versions:
17.4.0
Product / Package Ecosystem Affected Versions Fixed Version
oauthenticator
PyPI
< 17.4.0
17.4.0

References

Frequently Asked Questions

What is CVE-2026-33175?
CVE-2026-33175 is a security vulnerability in Oauthenticator involving Auth0OAuthenticator has an Authentication Bypass via Unverified Email Claims under CWE-287: Improper Authentication.
Which Oauthenticator versions are affected?
Affected versions include releases prior to 17.4.0 across affected packages: oauthenticator.
What version fixes CVE-2026-33175?
Upgrading to 17.4.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is oauthenticator affected?
Yes, oauthenticator is affected in releases prior to 17.4.0. Upgrade your dependency to 17.4.0 or later.
What is the CVSS score of CVE-2026-33175?
CVE-2026-33175 has a CVSS v3.1 base score of 8.8 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-33175?
CVE-2026-33175 is classified under CWE-287: Improper Authentication (When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.).
How can I check PyPI dependencies for CVE-2026-33175?
Run the dependency tree command: 'pip show oauthenticator'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-rrvg-cxh4-qhrv",
  "modified" : "2026-04-06T23:09:50Z",
  "published" : "2026-04-03T21:35:37Z",
  "aliases" : [ "CVE-2026-33175" ],
  "summary" : "Auth0OAuthenticator has an Authentication Bypass via Unverified Email Claims",
  "details" : "### Summary\n\nAn 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.\n\n### Impact\n\nThis 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.\n\n### Patches\n\n- Upgrade oauthenticator to 17.4\n\n### Workarounds\n\n- Check `email_verified` field in an `Authenticator.post_auth_hook` function\n- Do not use `email` as the username claim\n- [Enforce email verification in auth0](https://support.auth0.com/center/s/article/Enforce-Email-Verification-With-Sending-Email-After-Each-Denied-Access)",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "oauthenticator"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "17.4.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/jupyterhub/oauthenticator/security/advisories/GHSA-rrvg-cxh4-qhrv"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-33175"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/jupyterhub/oauthenticator/commit/f0c7002dc36e41efae0f674033cf7888a21d96f9"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/jupyterhub/oauthenticator"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/jupyterhub/oauthenticator/releases/tag/17.4.0"
  }, {
    "type" : "WEB",
    "url" : "https://support.auth0.com/center/s/article/Enforce-Email-Verification-With-Sending-Email-After-Each-Denied-Access"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-287", "CWE-290" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-03T21:35:37Z",
    "nvd_published_at" : "2026-04-03T22:16:26Z"
  }
}