Skip to main content
VulnerabilityPublished

CVE-2026-5422: jupyter/jupyter · Relative Path Traversal

Affects jupyter/jupyterSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.8 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.0 base score
6.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
4.8% chance of exploitation in 30 days – higher than 92% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
jupyterjupyter/jupyterAffected
  • ≥ unspecified, ≤ latest
Fixed in–

AI-suggested

Until an official fix is available, restrict access to trusted users only and consider isolating the jupyter-server environment to limit potential impact.

Description

CVE-2026-5422 is a path traversal vulnerability in jupyter-server version 2.17.0 caused by improper root directory boundary checks in path handling functions. This flaw allows attackers to bypass directory restrictions and access files in sibling directories, potentially exposing sensitive data in shared hosting environments. The vulnerability arises from a startswith check without a trailing path separator and failure to remove '..' path segments. No patch or official remediation is currently confirmed.

References

Community reviews

Loading reviews…