ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-5422

A path traversal vulnerability exists in jupyter-server version 2.17.0 due to an incorrect root directory boundary check in the _get_os_path() function within jupyter_…

Published Jun 2, 2026 · catalog updated Jul 22, 2026 · jupyter server

Check if you run it

No confirmed exploitation is on record for CVE-2026-5422. EPSS is 0.55%. Act only if a listed version of jupyter server is installed.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High8.1
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.55%
Remediation
Not established
Affected products
cpe jupyter/jupyter server

A path traversal vulnerability exists in jupyter-server version 2.17.0 due to an incorrect root directory boundary check in the _get_os_path() function within jupyter_server/services/contents/fileio.py. The check uses startswith(root) without appending a trailing path separator, allowing sibling directories with names starting with the same prefix as root_dir to bypass the check. Additionally, the to_os_path() function in utils.py does not strip ".." from path parts, enabling traversal sequences to bypass the vulnerable check. This vulnerability can lead to unauthorized read/write access to files in sibling directories, potentially exposing sensitive data in shared hosting environments.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe jupyter/jupyter server2.17.0

How to fix CVE-2026-5422

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-5422. EPSS is 0.55%. Act only if a listed version of jupyter server is installed.

Which versions are affected?

Compare what you have installed with jupyter/jupyter server 2.17.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-23. EPSS 0.55%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Jun 2, 2026 · NIST NVD

    Detected

    A path traversal vulnerability exists in jupyter-server version 2.17.0 due to an incorrect root directory boundary check in the _get_os_path() function within jupyter_server/services/contents/fileio.py. The check uses startswith(root) without appending a trailing path separator, allowing sibling directories with names starting with the same prefix as root_dir to bypass the check. Additionally, the

  2. Jul 22, 2026 · NIST NVD

    Updated

    A path traversal vulnerability exists in jupyter-server version 2.17.0 due to an incorrect root directory boundary check in the _get_os_path() function within jupyter_server/services/contents/fileio.py. The check uses startswith(root) without appending a trailing path separator, allowing sibling directories with names starting with the same prefix as root_dir to bypass the check. Additionally, the

Sources

  • CVE.orgVulnerability recordCVE-2026-5422

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-5422

    30-day exploitation probability 0.55%

    first.org
  • NIST NVDVulnerability recordCVE-2026-5422

    A path traversal vulnerability exists in jupyter-server version 2.17.0 due to an incorrect root directory boundary check in the _get_os_path() function within jupyter_server/services/contents/fileio.py. The check uses startswith(root) without appending a trailing path separator,

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 23, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.