Summary
Workarounds
No workaround has been identified, however users should ensure to upgrade jupyter-server to version 2.7.2 or newer which includes a redirect vulnerability fix.
References
Vulnerability reported by user @davwwwx via the bug bounty program sponsored by the European Commission and hosted on the Intigriti platform.
Impact
Users of JupyterLab who click on a malicious link may get their Authorization and XSRFToken tokens exposed to a third party when running an older jupyter-server version.
CVE-2024-22421 has a CVSS score of 7.6 (High). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.0.11, 3.6.7, 7.0.7); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
JupyterLab 4.1.0b2, 4.0.11, and 3.6.7 were patched.
Frequently Asked Questions
- What is CVE-2024-22421? CVE-2024-22421 is a high-severity security vulnerability in jupyterlab (pip), affecting versions >= 4.0.0, <= 4.0.10. It is fixed in 4.0.11, 3.6.7, 7.0.7.
- How severe is CVE-2024-22421? CVE-2024-22421 has a CVSS score of 7.6 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which packages are affected by CVE-2024-22421?
jupyterlab(pip) (versions >= 4.0.0, <= 4.0.10)notebook(pip) (versions >= 7.0.0, <= 7.0.6)
- Is there a fix for CVE-2024-22421? Yes. CVE-2024-22421 is fixed in 4.0.11, 3.6.7, 7.0.7. Upgrade to this version or later.
- Is CVE-2024-22421 exploitable, and should I be worried? Whether CVE-2024-22421 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2024-22421 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2024-22421?
- Upgrade
jupyterlabto 4.0.11 or later - Upgrade
jupyterlabto 3.6.7 or later - Upgrade
notebookto 7.0.7 or later
- Upgrade