CVE-2020-26215: Open redirect in Jupyter Notebook
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
- CWE
- CWE-601
Report tools
Action score
24
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.
Is your version affected? Check itNoroxi 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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| jupyter | notebook | cpe:2.3:a:jupyter:notebook |
| debian | debian linux | cpe:2.3:o:debian:debian_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.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | jupyter-notebook | before 6.1.5-1 | 6.1.5-1 |
| Debian:9 | jupyter-notebook | before 4.2.3-4+deb9u2 | 4.2.3-4+deb9u2 |
| openSUSE:Leap 15.1 | python-jupyter_notebook | before 5.7.7-lp151.2.3.1 | 5.7.7-lp151.2.3.1 |
| openSUSE:Leap 15.2 | python-notebook | before 5.7.8-lp152.2.3.1 | 5.7.8-lp152.2.3.1 |
| PyPI | notebook | before 6.1.5 | 6.1.5 |
| SUSE:Package Hub 15 SP1 | python-jupyter_notebook | before 5.7.7-bp151.3.3.1 | 5.7.7-bp151.3.3.1 |
Same product
jupyter: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-32798Failure to Sanitize Special Elements into a Different Plane (Special Element Injection) in notebook39Monitor
- CVE-2026-40171Jupyter Notebook and JupyterLab token theft via stored XSS in help command linker33Monitor
- 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 Notebook30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| jupyter notebook | 6.1.5 · description | Vendor (CNA) |
| debian:jupyter-notebook | 6.1.5-1 · Debian:12 | Package registry (OSV) |
| opensuse:python-jupyter_notebook | 5.7.7-lp151.2.3.1 · openSUSE:Leap 15.1 | Package registry (OSV) |
| opensuse:python-notebook | 5.7.8-lp152.2.3.1 · openSUSE:Leap 15.2 | Package registry (OSV) |
| PyPI:notebook | 6.1.5 | Package registry (OSV) |
| suse:python-jupyter_notebook | 5.7.7-bp151.3.3.1 · SUSE:Package Hub 15 SP1 | Package 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
Weakness class (CWE)
CWE-601 · URL Redirection to Untrusted Site ('Open Redirect')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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.