CVE-2026-33175

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 65% of all CVEs by exploit prediction. 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.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

OAuthenticator is software that allows OAuth2 identity providers to be plugged in and used with JupyterHub. Prior to version 17.4.0, 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. This issue has been patched in version 17.4.0.

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
35.3%
KEV
Not listed

Published

April 3, 2026

Last Modified

April 15, 2026

Advisory Details (3)

Auto-updated May 23, 2026
Patch available. Sources: github.
github Patch Available

Authentication Bypass in Auth0OAuthenticator via Unverified Email Claims · Advisory · jupyterhub/oauthenticator · GitHub

https://github.com/jupyterhub/oauthenticator/security/advisories/GHSA-rrvg-cxh4-qhrv
generic

Release 17.4.0 · jupyterhub/oauthenticator · GitHub

https://github.com/jupyterhub/oauthenticator/releases/tag/17.4.0
generic

Merge commit from fork · jupyterhub/oauthenticator@f0c7002 · GitHub

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

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
oauthenticator0.1.0 ... 17.3.0 (49 versions)17.4.0—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 41× 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.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-33175?
CVE-2026-33175 is a high vulnerability published on April 3, 2026. OAuthenticator is software that allows OAuth2 identity providers to be plugged in and used with JupyterHub. Prior to version 17.4.0, 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…
When was CVE-2026-33175 disclosed?
CVE-2026-33175 was first published in the National Vulnerability Database on April 3, 2026, 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-2026-33175 actively exploited?
CVE-2026-33175 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 35.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-33175?
CVE-2026-33175 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-33175?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-33175, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-33175

Explore →

Is Your Infrastructure Affected by CVE-2026-33175?

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

Start Free Scan →Browse All CVEs