Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2020-26215: Open redirect in Jupyter Notebook

MediumCVSS 6.1 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 24/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.2% (FIRST EPSS); higher than 69.3% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
  • Fixed version: jupyter notebook 6.1.5.

Low priority for now. Upgrade to jupyter notebook 6.1.5 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Jupyter Notebook before version 6.1.5 has an 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. The issue is patched in version 6.1.5.

Published
Nov 18, 2020
Updated
Jun 16, 2026
EPSS
1.2% · 69th percentile

Report tools

JSON

Action score

24

Monitor

Low priority for now.

CVSS
24 / 40 · 6.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.2%

CNA vs NVD score

NVD
6.1
CNA · GitHub_M
4.4
1.7 point gap

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:N/I:L/A:L

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2020-26215

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
jupyternotebook
debiandebian linux

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • jupyter notebook

    • < 6.1.5affected

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux9.0
  • jupyter notebookbefore 6.1.5

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12jupyter-notebookbefore 6.1.5-16.1.5-1
Debian:9jupyter-notebookbefore 4.2.3-4+deb9u24.2.3-4+deb9u2
openSUSE:Leap 15.1python-jupyter_notebookbefore 5.7.7-lp151.2.3.15.7.7-lp151.2.3.1
openSUSE:Leap 15.2python-notebookbefore 5.7.8-lp152.2.3.15.7.8-lp152.2.3.1
PyPInotebookbefore 6.1.56.1.5
SUSE:Package Hub 15 SP1python-jupyter_notebookbefore 5.7.7-bp151.3.3.15.7.7-bp151.3.3.1

Other highest-scoring records for the same primary product.

  • CVE-2021-32798Failure to Sanitize Special Elements into a Different Plane (Special Element Injection) in notebook
    39Monitor
  • CVE-2026-40171Jupyter Notebook and JupyterLab token theft via stored XSS in help command linker
    33Monitor
  • CVE-2018-8768In Jupyter Notebook before 5.4.1, a maliciously forged notebook file can bypass sanitization to execute JavaScript in the notebook context.
    31Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2019-10856Apr 4, 2019 · In Jupyter Notebook before 5.7.8, an open redirect can occur via an empty netloc.
    24Monitor
  • ← EarlierCVE-2018-21030Oct 31, 2019 · Jupyter Notebook before 5.5.0 does not use a CSP header to treat served files as belonging to a separate origin.
    21Monitor
  • Later →CVE-2022-24758Mar 31, 2022 · Insertion of Sensitive Information into Log File affects Jupyter Notebook
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
jupyter notebook6.1.5 · descriptionVendor (CNA)
debian:jupyter-notebook6.1.5-1 · Debian:12Package registry (OSV)
opensuse:python-jupyter_notebook5.7.7-lp151.2.3.1 · openSUSE:Leap 15.1Package registry (OSV)
opensuse:python-notebook5.7.8-lp152.2.3.1 · openSUSE:Leap 15.2Package registry (OSV)
PyPI:notebook6.1.5Package registry (OSV)
suse:python-jupyter_notebook5.7.7-bp151.3.3.1 · SUSE:Package Hub 15 SP1Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
low · data or configuration can be modified
Availability
none

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality impact
Low
Integrity impact
Low
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

References

All records