https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T05:00:31.170060+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/cleanstart-2026-an27706 Withdrawn: CLEANSTART-2026-AN27706 — Security fixes for CVE-2026-22815, CVE-2026-30922, CVE-2026-31958, CVE-2026-32597, CVE-2026-33175, CVE-2026-34052, CVE-… 2026-10-03T05:00:31.252271+00:00

Withdrawn by the publisher.

Affected: CleanStart: jupyterhub-k8s-hub

Multiple security vulnerabilities affect the jupyterhub-k8s-hub package. These issues are resolved in later releases. See references for individual vulnerability details.

 https://cve.radiocsirt.org/vuln/euvd-2026-281094 EUVD-2026-281094 2026-10-03T05:00:31.252332+00:00 EUVD-2026-281094 https://cve.radiocsirt.org/vuln/fkie_cve-2026-33175 fkie_cve-2026-33175 2026-10-03T05:00:31.252349+00:00

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.

 https://cve.radiocsirt.org/vuln/ghsa-rrvg-cxh4-qhrv GHSA-rrvg-cxh4-qhrv — Auth0OAuthenticator has an Authentication Bypass via Unverified Email Claims 2026-10-03T05:00:31.252374+00:00

Affected: PyPI: oauthenticator

### Summary

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.

### Impact

This is an **Authentication Bypass Vulnerability**. Any Auth0 tenant leveraging the `Auth0OAuthenticator` mapping the `email` claim to the JupyterHub username is impacted. By default, Auth0 handles email verification as a user flag, not a hard block to authentication streams. If an attacker can register an account with the Auth0 tenant with an unverified email and knows the email of an existing user on the system, they can authenticate as that user.

### Patches

- Upgrade oauthenticator to 17.4

### Workarounds

- Check `email_verified` field in an `Authenticator.post_auth_hook` function - Do not use `email` as the username claim - [Enforce email verification in auth0](https://support.auth0.com/center/s/article/Enforce-Email-Verification-With-Sending-Email-After-Each-Denied-Access)

 https://cve.radiocsirt.org/vuln/pysec-2026-2238 PYSEC-2026-2238 2026-10-03T05:00:31.252408+00:00

Affected: PyPI: oauthenticator

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.