High

Globus `identity_provider` restriction ignored when used with `allow_all` in JupyterHub 5.0

  • Disclosed: 12.06.2024
  • Updated: 11.10.2026 15:17

Impact

JupyterHub < 5.0, when used with GlobusOAuthenticator, could be configured to allow all users from a particular institution only. The configuration for this would look like:

python
# Require users to be using the "foo.horse" identity provider, often an institution or university
c.GlobusAuthenticator.identity_provider = "foo.horse"
# Allow everyone who has that identity provider to log in
c.GlobusAuthenticator.allow_all = True

This worked fine prior to JupyterHub 5.0, because allow_all did not take precedence over identity_provider.

Since JupyterHub 5.0, allow_all does take precedence over identity_provider. On a hub with the same config, now all users will be allowed to login, regardless of identity_provider. identity_provider will basically be ignored.

This is a documented change in JupyterHub 5.0, but is likely to catch many users by surprise.

Patches

OAuthenticator 16.3.1 fixes the issue with JupyterHub 5.0, and does not affect previous versions.

Workarounds

Do not upgrade to JupyterHub 5.0 when using GlobusOAuthenticator in the prior configuration.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Python (PyPI) oauthenticator < 16.3.1 16.3.1

References

CVSS score 8.1/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Weakness (CWE)
CWE-863
Platform
Python (PyPI)
Package
oauthenticator
Disclosed
12.06.2024
Updated
11.10.2026 15:17

Sources and licenses

OSV / GitHub Advisory Database - PYSEC-2026-1711 - PyPA Advisory Database; CC BY 4.0

OSV / GitHub Advisory Database - GHSA-gprj-3p75-f996 - CC BY 4.0

Vulnerability history: oauthenticator

All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.

Total entries
6
First → latest
02.2018 04.2026
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • High 5
  • Medium 1

Disclosures per year

  1. 2018: 1
  2. 2019: 0
  3. 2020: 1
  4. 2021: 0
  5. 2022: 1
  6. 2023: 0
  7. 2024: 2
  8. 2025: 0
  9. 2026: 1
  1. Globus `identity_provider` restriction ignored when used with `allow_all` in JupyterHub 5.0 this entry
    High · 8.1 CVE-2024-37300 < 16.3.1 16.3.1
  2. High · 6.3 CVE-2020-26250 >= 0.12.0, < 0.12.2 0.12.2
  3. High · 8.8 CVE-2018-7206 >= 0.6, < 0.6.2, >= 0.7, < 0.7.3 0.6.2, 0.7.3

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.