Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The oauthenticator package, versions before 17.4.0, is vulnerable when used with Auth0OAuthenticator and the email claim is set as the username claim. An attacker who registers on the Auth0 tenant with an unverified email address that matches an existing user can log in to JupyterHub as that user. Upgrade oauthenticator to 17.4.0 or later. Alternatively, stop using email as the username claim, or check the email_verified field in a post_auth_hook.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 8.8 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0045, the 39th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:11 UTC First seen by agentprime
- 31 Oct 2026, 14:11 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-rrvg-cxh4-qhrv
- OSV: GHSA-rrvg-cxh4-qhrv
- github.com/jupyterhub/oauthenticator/security/advisories/GHSA-rrvg-cxh4-qhrv
- nvd.nist.gov/vuln/detail/CVE-2026-33175
- github.com/jupyterhub/oauthenticator/commit/f0c7002dc36e41efae0f674033cf7888a21d96f9
- github.com/jupyterhub/oauthenticator
- github.com/jupyterhub/oauthenticator/releases/tag/17.4.0
- support.auth0.com/center/s/article/Enforce-Email-Verification-With-Sending-Email-After-Each-Denied-Access