CVE-2024-22421: PYSEC-2026-2534 - JupyterLab vulnerable to potential authentication and CSRF tokens leak

CVE-2024-22421 · Severity: low · CVSS 3.1 · Published 2026-07-13

JupyterLab vulnerable to potential authentication and CSRF tokens leak

Technologies: jupyterlab (PyPI), notebook (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2024-22421 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2024-22421 being exploited in the wild.
How severe is CVE-2024-22421?
Low severity, with a CVSS score of 3.1, published 13 July 2026.
Which products and versions are affected?
jupyterlab (PyPI) ECOSYSTEM:introduced=0,fixed=3.6.7,introduced=4.0.0,fixed=4.0.11, ECOSYSTEM:introduced=4.0.0,fixed=4.0.11; notebook (PyPI) ECOSYSTEM:introduced=7.0.0,fixed=7.0.7.
Is there a fix for CVE-2024-22421?
Yes. jupyterlab (PyPI): upgrade to 4.0.11 or later; notebook (PyPI): upgrade to 7.0.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2024-22421?
Check whether you run jupyterlab (PyPI) or notebook (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

  • jupyterlab (PyPI): upgrade to 4.0.11 or later
    pip install "jupyterlab>=4.0.11"
  • notebook (PyPI): upgrade to 7.0.7 or later
    pip install "notebook>=7.0.7"

Affected products

  • jupyterlab (PyPI) ECOSYSTEM:introduced=0,fixed=3.6.7,introduced=4.0.0,fixed=4.0.11, ECOSYSTEM:introduced=4.0.0,fixed=4.0.11
  • notebook (PyPI) ECOSYSTEM:introduced=7.0.0,fixed=7.0.7

Identifiers

  • CVE-2024-22421
  • GHSA-44cc-43rp-5947
  • PYSEC-2026-1706
  • PYSEC-2026-2534

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.