Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The oauthenticator package before 16.3.1 is affected when used with JupyterHub 5.0 and the Globus authenticator. On such a hub, an identity_provider restriction is ignored when allow_all is also set, so all users can log in regardless of their institution. Upgrade oauthenticator to 16.3.1 or later; the source does not list a workaround beyond avoiding JupyterHub 5.0 with this configuration.
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.1 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0040, the 35th percentile, on 21 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:35 UTC First seen by agentprime
- 31 Oct 2026, 14:35 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-gprj-3p75-f996
- OSV: GHSA-gprj-3p75-f996
- github.com/jupyterhub/oauthenticator/security/advisories/GHSA-gprj-3p75-f996
- nvd.nist.gov/vuln/detail/CVE-2024-37300
- github.com/jupyterhub/oauthenticator/commit/d1aea05fa89f2beae15ab0fa0b0d071030f79654
- github.com/jupyterhub/oauthenticator
- jupyterhub.readthedocs.io/en/stable/howto/upgrading-v5.html#authenticator-allow-all-and-allow-existing-users