CVE-2020-26215

Open redirect in Jupyter Notebook

Patched in notebook 6.1.5

References

OWASP page on open redirects

For more information

If you have any questions or comments about this advisory, or vulnerabilities to report, please email our security list [email protected].

Credit: zhuonan li of Alibaba Application Security Team

What kind of vulnerability is it? Who is impacted?

Open redirect vulnerability - a maliciously crafted link to a notebook server could redirect the browser to a different website.

All notebook servers are technically affected, however, these maliciously crafted links can only be reasonably made for known notebook server hosts. A link to your notebook server may appear safe, but ultimately redirect to a spoofed server on the public internet.

Untrusted input controls a URL used for redirection, which can forward users to attacker-controlled sites. Typical impact: phishing and credential harvesting via a trusted domain.

CVE-2020-26215 has a CVSS score of 4.4 (Low). The vector is network-reachable, low 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 (6.1.5); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Has the problem been patched? What versions should users upgrade to?

1. What is CVE-2020-26215? CVE-2020-26215 is a low-severity open redirect vulnerability in notebook (pip), affecting versions <= 6.1.4. It is fixed in 6.1.5. Untrusted input controls a URL used for redirection, which can forward users to attacker-controlled sites.
2. How severe is CVE-2020-26215? CVE-2020-26215 has a CVSS score of 4.4 (Low). 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.
3. Which versions of notebook are affected by CVE-2020-26215? notebook (pip) versions <= 6.1.4 is affected.
4. Is there a fix for CVE-2020-26215? Yes. CVE-2020-26215 is fixed in 6.1.5. Upgrade to this version or later.
5. Is CVE-2020-26215 exploitable, and should I be worried? Whether CVE-2020-26215 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
6. What actually determines whether CVE-2020-26215 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.
7. How do I fix CVE-2020-26215? Upgrade notebook to 6.1.5 or later.

Other vulnerabilities in notebook