In Jupyter Notebook before 5.4.1, a maliciously forged notebook file can bypass sanitization to execute JavaScript in the notebook context.
In Jupyter Notebook before 5.4.1, a maliciously forged notebook file can bypass sanitization to execute JavaScript in the notebook context. Specifically, invalid HTML is 'fixed' by jQuery after sanitization, making it dangerous.
- Published
- Mar 18, 2018
- Updated
- Jun 16, 2026
- EPSS
- 1.1% · 64th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.1%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| jupyter | notebook | cpe:2.3:a:jupyter:notebook |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- jupyter notebookbefore 5.4.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | ipython | before 5.1.0-2 | 5.1.0-2 |
| Debian:12 | jupyter-notebook | before 5.4.1-1 | 5.4.1-1 |
| Debian:9 | jupyter-notebook | before 4.2.3-4+deb9u1 | 4.2.3-4+deb9u1 |
| PyPI | notebook | before 5.4.1 | 5.4.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-2022-24758Insertion of Sensitive Information into Log File affects Jupyter Notebook30Monitor
- CVE-2020-26215Open redirect in Jupyter Notebook24Monitor
- CVE-2019-10856In Jupyter Notebook before 5.7.8, an open redirect can occur via an empty netloc.24Monitor
- CVE-2018-19352Jupyter Notebook before 5.7.2 allows XSS via a crafted directory name because notebook/static/tree/js/notebooklist.js handles certain URLs u24Monitor
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 |
|---|---|---|
| debian:ipython | 5.1.0-2 · Debian:12 | Package registry (OSV) |
| debian:jupyter-notebook | 5.4.1-1 · Debian:12 | Package registry (OSV) |
| PyPI:notebook | 5.4.1 | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system 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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- openwall.com/lists/oss-security/2018/03/15/2
- lists.debian.org/debian-lts-announce/2020/11/msg00033.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.