CVE-2024-37300

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.4% (32nd percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

OAuthenticator is software that allows OAuth2 identity providers to be plugged in and used with JupyterHub. JupyterHub < 5.0, when used with GlobusOAuthenticator, could be configured to allow all users from a particular institution only. 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. OAuthenticator 16.3.1 fixes the issue with JupyterHub 5.0, and does not affect previous versions. As a workaround, do not upgrade to JupyterHub 5.0 when using GlobusOAuthenticator in the prior configuration.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
32nd
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

June 12, 2024

Last Modified

April 15, 2026

Advisory Details (3)

Auto-updated Sep 16, 2026
Patch available. Sources: github_commit, github.
generic

Upgrading to JupyterHub 5 — JupyterHub documentation

https://jupyterhub.readthedocs.io/en/stable/howto/upgrading-v5.html#authenticator-allow-all-and-allow-existing-users
githubMentions a patch (unverified)

Globus `identity_provider` restriction ignored when used with `allow_all` in JupyterHub 5.0 · Advisory · jupyterhub/oauthenticator · GitHub

https://github.com/jupyterhub/oauthenticator/security/advisories/GHSA-gprj-3p75-f996
github_commit

commit d1aea05fa89f (jupyterhub/oauthenticator)

Fix landed in jupyterhub/oauthenticator commit d1aea05fa89f — awaiting tagged release

https://github.com/jupyterhub/oauthenticator/commit/d1aea05fa89f2beae15ab0fa0b0d071030f79654

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
oauthenticator0.1.0 ... 16.3.0 (44 versions)
  • every version up to 16.3.1: fixed in 16.3.1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 34× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 206 total refreshes for this CVE.

  1. 2026-10-10 19:58 UTCEPSS rescore
  2. 2026-10-09 20:05 UTCEPSS rescore
  3. 2026-10-08 17:07 UTCEPSS rescore
  4. 2026-10-07 23:46 UTCEPSS rescore
  5. 2026-10-07 11:24 UTCOSV refresh
  6. 2026-10-06 15:15 UTCEPSS rescore
  7. 2026-10-05 17:41 UTCEPSS rescore
  8. 2026-10-04 23:20 UTCEPSS rescore
  9. 2026-10-03 14:24 UTCEPSS rescore
  10. 2026-10-01 19:48 UTCEPSS rescore
  11. 2026-09-30 19:47 UTCEG score recompute
  12. 2026-09-30 15:01 UTCEPSS rescore
  13. 2026-09-30 15:01 UTCEPSS rescore
  14. 2026-09-29 15:17 UTCEPSS rescore
  15. 2026-09-28 13:49 UTCEPSS rescore
  16. 2026-09-27 13:44 UTCEPSS rescore
  17. 2026-09-26 15:57 UTCEPSS rescore
  18. 2026-09-26 00:23 UTCEPSS rescore
  19. 2026-09-24 14:01 UTCEPSS rescore
  20. 2026-09-23 13:46 UTCEPSS rescore
  21. 2026-09-22 14:46 UTCEPSS rescore
  22. 2026-09-21 20:32 UTCEPSS rescore
  23. 2026-09-20 20:14 UTCEPSS rescore
  24. 2026-09-20 20:14 UTCEPSS rescore
  25. 2026-09-19 15:40 UTCEPSS rescore
Show 75 more
  1. 2026-09-18 19:26 UTCEPSS rescore
  2. 2026-09-17 17:36 UTCOSV refresh
  3. 2026-09-16 14:06 UTCEPSS rescore
  4. 2026-09-15 03:08 UTCEPSS rescore
  5. 2026-09-15 03:08 UTCEPSS rescore
  6. 2026-09-13 16:45 UTCEPSS rescore
  7. 2026-09-12 14:59 UTCEPSS rescore
  8. 2026-09-11 14:51 UTCEPSS rescore
  9. 2026-09-11 09:35 UTCEPSS rescore
  10. 2026-09-08 21:58 UTCEPSS rescore
  11. 2026-09-07 16:00 UTCEPSS rescore
  12. 2026-09-07 15:59 UTCEPSS rescore
  13. 2026-09-06 13:46 UTCEPSS rescore
  14. 2026-09-05 15:26 UTCEPSS rescore
  15. 2026-09-04 13:59 UTCEPSS rescore
  16. 2026-09-04 05:05 UTCEPSS rescore
  17. 2026-09-02 14:10 UTCEPSS rescore
  18. 2026-09-01 13:52 UTCEPSS rescore
  19. 2026-09-01 04:37 UTCEPSS rescore
  20. 2026-08-30 19:15 UTCEPSS rescore
  21. 2026-08-30 01:20 UTCEPSS rescore
  22. 2026-08-29 17:43 UTCOSV refresh
  23. 2026-08-28 21:39 UTCEPSS rescore
  24. 2026-08-27 14:23 UTCEPSS rescore
  25. 2026-08-26 14:44 UTCEPSS rescore
  26. 2026-08-25 13:47 UTCEPSS rescore
  27. 2026-08-24 14:15 UTCEPSS rescore
  28. 2026-08-23 00:18 UTCEPSS rescore
  29. 2026-08-21 23:47 UTCEPSS rescore
  30. 2026-08-20 22:53 UTCEPSS rescore
  31. 2026-08-19 17:02 UTCEPSS rescore
  32. 2026-08-18 13:46 UTCEPSS rescore
  33. 2026-08-17 13:45 UTCEPSS rescore
  34. 2026-08-16 14:54 UTCEPSS rescore
  35. 2026-08-16 02:13 UTCEPSS rescore
  36. 2026-08-15 01:28 UTCEPSS rescore
  37. 2026-08-13 21:59 UTCEPSS rescore
  38. 2026-08-13 04:43 UTCOSV refresh
  39. 2026-08-12 13:49 UTCEPSS rescore
  40. 2026-08-11 13:40 UTCEPSS rescore
  41. 2026-08-10 23:58 UTCEPSS rescore
  42. 2026-08-09 13:45 UTCEPSS rescore
  43. 2026-08-08 16:35 UTCEPSS rescore
  44. 2026-08-07 16:25 UTCEPSS rescore
  45. 2026-08-06 13:45 UTCEPSS rescore
  46. 2026-08-05 19:16 UTCEPSS rescore
  47. 2026-08-04 15:08 UTCEPSS rescore
  48. 2026-08-04 10:36 UTCEPSS rescore
  49. 2026-08-03 10:34 UTCEPSS rescore
  50. 2026-08-03 10:34 UTCEPSS rescore
  51. 2026-08-02 02:25 UTCEPSS rescore
  52. 2026-08-01 04:14 UTCEPSS rescore
  53. 2026-08-01 04:14 UTCEPSS rescore
  54. 2026-07-30 16:26 UTCEPSS rescore
  55. 2026-07-30 16:26 UTCEPSS rescore
  56. 2026-07-30 01:29 UTCEPSS rescore
  57. 2026-07-28 15:34 UTCEPSS rescore
  58. 2026-07-28 12:50 UTCOSV refresh
  59. 2026-07-27 14:11 UTCEPSS rescore
  60. 2026-07-26 14:53 UTCEPSS rescore
  61. 2026-07-25 14:16 UTCEPSS rescore
  62. 2026-07-24 14:16 UTCEPSS rescore
  63. 2026-07-23 14:17 UTCEPSS rescore
  64. 2026-07-23 14:17 UTCEPSS rescore
  65. 2026-07-23 02:38 UTCEG score recompute
  66. 2026-07-22 14:07 UTCEPSS rescore
  67. 2026-07-22 14:07 UTCEPSS rescore
  68. 2026-07-21 15:23 UTCEPSS rescore
  69. 2026-07-21 15:23 UTCEPSS rescore
  70. 2026-07-20 17:06 UTCEPSS rescore
  71. 2026-07-19 14:30 UTCEPSS rescore
  72. 2026-07-19 14:30 UTCEPSS rescore
  73. 2026-07-19 02:28 UTCEPSS rescore
  74. 2026-07-19 02:28 UTCEPSS rescore
  75. 2026-07-18 10:03 UTCEPSS rescore

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2024-37300?
CVE-2024-37300 is a high vulnerability published on June 12, 2024. OAuthenticator is software that allows OAuth2 identity providers to be plugged in and used with JupyterHub. JupyterHub < 5.0, when used with GlobusOAuthenticator, could be configured to allow all users from a particular institution only. This worked fine prior to JupyterHub 5.0, because allowall…
When was CVE-2024-37300 disclosed?
CVE-2024-37300 was first published on June 12, 2024, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-37300 actively exploited?
CVE-2024-37300 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-37300?
CVE-2024-37300 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2024-37300?
A fix for CVE-2024-37300 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-37300

Explore →

Is Your Infrastructure Affected by CVE-2024-37300?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs