CVE-2026-33175: OAuthenticator is software that allows OAuth2 identity providers to be plugged in and used with JupyterHub

Q: How do I fix CVE-2026-33175?

oauthenticator: upgrade to 17.4.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-33175 being exploited?

CVE-2026-33175 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-33175 affect?

CVE-2026-33175 affects oauthenticator. Severity is high (CVSS 8.8). 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 addres

This month

HIGH 8.8UPGRADE

CVE-2026-33175 is a high-severity flaw (CVSS 8.8) affecting oauthenticator. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.4% (top 62%)
CISA exploited list	No
Weakness	CWE-287, CWE-290
Published	2026-04-03
Last modified	2026-07-24

Publisher (CNA): GitHub, Inc. · Vendor: jupyter

Last updated 2026-07-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-04-03 22:16 UTCPublished CVE record published
2026-07-24 22:10 UTCUpdated Record last modified

jupyter oauthenticator UPGRADE

Affected: < 17.4.0

Fixed in: 17.4.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy oauthenticator || rpm -q oauthenticator || oauthenticator --version

2. UPGRADE to 17.4.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade oauthenticator

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade oauthenticator

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-33175?

oauthenticator: upgrade to 17.4.0. Exact commands for each OS are on this page.

Is CVE-2026-33175 being exploited?

CVE-2026-33175 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-33175 affect?

CVE-2026-33175 affects oauthenticator. Severity is high (CVSS 8.8). 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 addres

How urgent is CVE-2026-33175?

Priority 40/100. High severity

Software pages

Auth0 vulnerabilities · Jupyter vulnerabilities

References

← Back to latest CVEs