# CVE-2022-29241: Jupyter server Token bruteforcing

Source: https://junglewise.ai/threats/cve-2022-29241-jupyter-server-token-bruteforcing  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2022-06-14  
License: CC BY 4.0 with a link back

CVE-2022-29241 · Severity: low · CVSS 3.1 · Published 2022-06-14

Jupyter Server provides the backend (i.e. the core services, APIs, and REST endpoints) for Jupyter web applications like Jupyter Notebook. Prior to version 1.17.1, if notebook server is started with a value of `root_dir` that contains the starting user's home directory, then the underlying REST API can be used to leak the access token assigned at start time by guessing/brute forcing the PID of the jupyter server. While this requires an authenticated user session, this URL can be used from a cross-site scripting payload or from a hooked or otherwise compromised browser to leak this access token to a malicious third party. This token can be used along with the REST API to interact with Jupyter services/notebooks such as modifying or overwriting critical files, such as .bashrc or .ssh/authorized_keys, allowing a malicious user to read potentially sensitive data and possibly gain control of the impacted system. This issue is patched in version 1.17.1.

Technologies: [jupyter-server (PyPI)](https://junglewise.ai/threats/technologies/pypi-jupyter-server). Vendors: [PyPI](https://junglewise.ai/threats/vendors/pypi).

## Quick answers

**Is CVE-2022-29241 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2022-29241 being exploited in the wild.

**How severe is CVE-2022-29241?** Low severity, with a CVSS score of 3.1, published 14 June 2022.

**Which products and versions are affected?** jupyter-server (PyPI) ECOSYSTEM:introduced=0,fixed=1.17.0, ECOSYSTEM:introduced=0,fixed=1.17.1.

**Is there a fix for CVE-2022-29241?** Yes. jupyter-server (PyPI): upgrade to 1.17.0, 1.17.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2022-29241?** Check whether you run jupyter-server (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- jupyter-server (PyPI): upgrade to 1.17.0, 1.17.1 or later

  ```sh
  pip install "jupyter-server>=1.17.1"
  ```


## Affected products

- jupyter-server (PyPI) ECOSYSTEM:introduced=0,fixed=1.17.0, ECOSYSTEM:introduced=0,fixed=1.17.1

## Identifiers

- CVE-2022-29241
- GHSA-q874-g24w-4q9g
- PYSEC-2022-211

## Related threats

- [Jupyter Server authorization bypass in kernel gateway handlers](https://junglewise.ai/threats/cve-2026-114135-jupyter-server-is-the-backend-for-jupyter-web-applications-from)
- [Jupyter Server token leakage in 5xx error logs](https://junglewise.ai/threats/cve-2026-86049-jupyter-server-token-leakage-in-5xx-error-logs)
- [Jupyter Server stored XSS in nbconvert handlers](https://junglewise.ai/threats/cve-2026-44727-jupyter-server-stored-xss-in-nbconvert-handlers)
- [Jupyter Jupyter Server CORS bypass via improper origin validation](https://junglewise.ai/threats/cve-2026-6657-jupyter-jupyter-server-cors-bypass-via-improper-origin-validation)
- [Jupyter jupyter-server path traversal in _get_os_path](https://junglewise.ai/threats/cve-2026-5422-jupyter-jupyter-server-path-traversal-in-get-os-path)