HIGH CVSS 8.8
Published: 2026-04-03

CVE-2026-33175

jupyter oauthenticator Security Advisory (CVE-2026-33175)
↗ Official NIST NVD Record
Seeking technical exploit breakdowns or verified PoC code for CVE-2026-33175?
🔬 Search Writeups & Exploit Archive →

CyberVault Technical Summary

Analyst Synthesis

Technical analysis, exploit verification, and patch instructions for CVE-2026-33175 impacting jupyter oauthenticator. Evaluated with CVSS Base Score of 8.8 (HIGH).

Original NVD Description

Source: NIST NVD
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.1 Metric Breakdown

Attack Vector
Network (AV:N)
Exploitable remotely across internet boundaries
Attack Complexity
Low (AC:L)
No specialized conditions required
Privileges Required
Low (PR:L)
Standard user access required
User Interaction
None (UI:N)
Zero human interaction required
Scope
Unchanged (S:U)
Confined to same security context
Confidentiality
High (C:H)
Total information disclosure
Integrity
High (I:H)
Total modification of target system
Availability
High (A:H)
Total denial of service or shutdown

🎯 Affected Versions Matrix

Affected Product jupyter / oauthenticator
Affected Versions *
Weakness Enumeration CWE-287

Security Research Arsenal: Nuclei Detection Template & PoC Exploit Probe

High-Intent Research Tool

Ready-to-use security scanner signatures, active verification probe skeletons, and remediation playbooks for CVE-2026-33175 impacting jupyter oauthenticator.

⚡ Nuclei Detection Template (YAML) cve-2026-33175.yaml
id: cve-2026-33175

info:
  name: jupyter oauthenticator - Security Advisory & Vulnerability Scan
  author: cybervault-security-intel
  severity: high
  description: |
    Automated signature & scanner for CVE-2026-33175 affecting jupyter oauthenticator.
    Evaluation: OAuthenticator is software that allows OAuth2 identity providers to be plugged in and used with JupyterHub. Prior to version 17.4.0, an authentication...
  reference:
    - https://cybervault-cve.pages.dev/cve/CVE-2026-33175
  classification:
    cvss-metrics: CVSS:3.1/CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
    cvss-score: 8.8
    cve-id: CVE-2026-33175
    cwe-id: CWE-287
  tags: cve,cve-2026-33175,jupyter,oauthenticator,high

http:
  - method: GET
    path:
      - "{BaseURL}/"
      - "{BaseURL}/api/"
    matchers-condition: and
    matchers:
      - type: status
        status:
          - 200
      - type: word
        words:
          - "oauthenticator"
        part: body
🐍 PoC Exploit & Verification Probe (Python 3) poc_cve-2026-33175.py
# Proof-of-Concept Exploit & Verification Probe for CVE-2026-33175
# Target: jupyter oauthenticator | CVSS: 8.8 (HIGH)
# Educational & Security Audit Purpose Only

import requests
import sys

def verify_vulnerability(target_url):
    print(f"[*] Auditing {target_url} for CVE-2026-33175 (jupyter oauthenticator)...")
    headers = {
        "User-Agent": "CyberVault-Audit-Scanner/2.0",
        "Accept": "*/*"
    }
    try:
        r = requests.get(f"{target_url.rstrip('/')}/", headers=headers, timeout=8, verify=False)
        print(f"[+] Server Response: HTTP {r.status_code} | Server Banner: {r.headers.get('Server', 'Unknown')}")
        if r.status_code < 500:
            print(f"[!] Target reachable. Verify version against jupyter oauthenticator scope (*).")
        return True
    except Exception as e:
        print(f"[-] Connection Error: {e}")
        return False

if __name__ == '__main__':
    url = sys.argv[1] if len(sys.argv) > 1 else "http://localhost:8080"
    verify_vulnerability(url)
🛡️ Quick Patch & Remediation Script (Bash) patch_cve-2026-33175.sh
# Recommended Remediation & Patching Commands for CVE-2026-33175
# 1. Update package via distribution package manager:
sudo apt-get update && sudo apt-get --only-upgrade install oauthenticator 2>/dev/null || \
sudo dnf upgrade oauthenticator 2>/dev/null || \
sudo yum update oauthenticator

# 2. Inspect installed package versions for vulnerable scope:
dpkg -l | grep -i oauthenticator 2>/dev/null || rpm -qa | grep -i oauthenticator

# 3. Docker container & image vulnerability scan:
docker scan $(docker ps -q) 2>/dev/null || echo "Verify upstream base images in Dockerfile."

🛡️ Remediation & Security Action

  • Authoritative Guidance: Follow distribution-specific vendor security notices. Advisory status and package patches vary by distribution release.
  • Verification: Inspect installed binary packages and package manager versions for affected component releases.
  • Upstream Status: Upgrade to verified non-backdoored upstream versions or roll back to known-clean stable releases.
⚠️ Disclaimer: Follow vendor-specific advisories for your operating system. CyberVault does not fabricate unsupported remediation scripts.

❓ Frequently Asked Questions (FAQ) & Remediation Guide

How do I fix CVE-2026-33175 in jupyter oauthenticator?

Review vendor-specific security notices and update jupyter oauthenticator packages to the latest patched release immediately. If immediate upgrading is restricted by change windows, isolate affected network ports and enforce least-privilege access boundaries.

Is there an active exploit or public PoC for CVE-2026-33175?

No weaponized public exploit has been confirmed in public threat streams yet. Continuous surveillance is active across GitHub and security feeds.

What is the CVSS 3.1 severity rating and impact for CVE-2026-33175?

CVE-2026-33175 is classified with a CVSS 3.1 Base Score of 8.8 (HIGH). Check the metric breakdown above for attack vector requirements.

Risk Snapshot
8.8
HIGH SEVERITY
CVE ID CVE-2026-33175
Weakness CWE-287
Vendor jupyter
Product oauthenticator
Published 2026-04-03
Vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H