{"answers":{"affected":"3 open source packages ship an affected version, including oauthenticator. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-33175 in the wild and no public exploit code.","fix":"Upgrade oauthenticator to 17.4.0 or later.","what":"CVE-2026-33175 is a high-severity authentication bypass vulnerability in jupyterhub oauthenticator, published on 3 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-33175 and fix it if it is affected.\n\nWhat it is: CVE-2026-33175 is a high-severity authentication bypass vulnerability in jupyterhub oauthenticator, published on 3 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-33175 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- oauthenticator (PyPI): affected all versions; fixed in 17.4.0\n- oauthenticator (PyPI): affected all versions; fixed in 17.4.0\n- oauthenticator (PyPI): affected all versions; fixed in 17.4.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-33175/ (Markdown: https://insights.sbomify.com/CVE-2026-33175/index.md)","id":"CVE-2026-33175","markdown":"https://insights.sbomify.com/CVE-2026-33175/index.md","name":"CVE-2026-33175","record":{"aliases":["CLEANSTART-2026-ZW90347","GHSA-rrvg-cxh4-qhrv","PYSEC-2026-2238"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"JupyterHub OAuth plugin","requires_auth":"low_privilege","summary":"Attackers with unverified Auth0 emails can bypass authentication and take over JupyterHub accounts when email is used as the username claim.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"oauthenticator","vendor":"jupyter"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-290","name":"Authentication Bypass by Spoofing"},{"id":"CWE-287","name":"Improper Authentication"}],"description":"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"OAuthenticator: Authentication Bypass in Auth0OAuthenticator via Unverified Email Claims","id":"CVE-2026-33175","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"Rails Active Support has a possible DoS vulnerability in its number helpers","id":"CVE-2026-33176"},"packages":[{"ecosystem":"PyPI","fixed":["17.4.0"],"introduced":["0"],"last_affected":[],"package":"oauthenticator","purl":null,"source":"GHSA-rrvg-cxh4-qhrv"},{"ecosystem":"PyPI","fixed":["17.4.0"],"introduced":["0"],"last_affected":[],"package":"oauthenticator","purl":"pkg:pypi/oauthenticator","source":"GHSA-rrvg-cxh4-qhrv"},{"ecosystem":"PyPI","fixed":["17.4.0"],"introduced":["0"],"last_affected":[],"package":"oauthenticator","purl":"pkg:pypi/oauthenticator","source":"PYSEC-2026-2238"}],"prev":{"headline":"Rails Active Storage has a possible DoS vulnerability when in proxy mode via Range requests","id":"CVE-2026-33174"},"products":["oauthenticator"],"published":"2026-04-03","related":[{"cvss_score":8.8,"headline":"JupyterHub OAuthenticator elevation of privilege","id":"CVE-2018-7206","kev_date_added":null,"published":"2018-02-18"},{"cvss_score":7.5,"headline":"GoogleOAuthenticator.hosted_domain incorrectly verifies membership of an Google organization/workspace","id":"CVE-2024-29033","kev_date_added":null,"published":"2024-03-20"},{"cvss_score":6.3,"headline":"Base class whitelist configuration ignored in OAuthenticator","id":"CVE-2020-26250","kev_date_added":null,"published":"2020-12-01"},{"cvss_score":4.2,"headline":"Authorization Bypass Through User-Controlled Key when using CILogonOAuthenticator in oauthenticator","id":"CVE-2022-31027","kev_date_added":null,"published":"2022-06-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-07","vendors":["jupyterhub"]},"summary":"Attackers with unverified Auth0 emails can bypass authentication and take over JupyterHub accounts when email is used as the username claim.","url":"https://insights.sbomify.com/CVE-2026-33175/"}