# CVE-2018-8768: Jupyter Notebook file bypasses sanitization, executes JavaScript

> Attackers can execute JavaScript in the notebook context by bypassing sanitization via invalid HTML, affecting Jupyter Notebook users.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 18 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-8768, GHSA-6cwv-x26c-w2q4, MGASA-2018-0182, PYSEC-2018-57, UBUNTU-CVE-2018-8768, USN-4855-1

## What is CVE-2018-8768?

CVE-2018-8768 is a high-severity cross-site scripting vulnerability in n/a, published on 18 Mar 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

## Which versions are affected by CVE-2018-8768?

3 open source packages ship an affected version, including notebook. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `notebook` | PyPI | All versions | 5.4.1 |
| `notebook` | PyPI | All versions | 5.4.1 |
| `notebook` | PyPI | All versions | 5.4.1 |

Products: Jupyter Notebook.

## How do I fix CVE-2018-8768?

Upgrade notebook to 5.4.1 or later.

## Is CVE-2018-8768 being exploited?

There is no known exploitation of CVE-2018-8768 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2021-32798](https://insights.sbomify.com/CVE-2021-32798/): Failure to Sanitize Special Elements into a Different Plane (Special Element Injection) in notebook (critical 10.0)
- [CVE-2022-24758](https://insights.sbomify.com/CVE-2022-24758/): Insertion of Sensitive Information into Log File affects Jupyter Notebook (high 7.5)
- [CVE-2019-10856](https://insights.sbomify.com/CVE-2019-10856/): Jupyter Notebook open redirect vulnerability (medium 6.1)
- [CVE-2018-19351](https://insights.sbomify.com/CVE-2018-19351/): Jupyter Notebook XSS via untrusted notebooks (medium 6.1)
- [CVE-2018-19352](https://insights.sbomify.com/CVE-2018-19352/): Jupyter Notebook XSS via directory name (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-8768 and fix it if it is affected.

What it is: CVE-2018-8768 is a high-severity cross-site scripting vulnerability in n/a, published on 18 Mar 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-8768 in the wild and no public exploit code.

Affected packages and fixed versions:
- notebook (PyPI): affected all versions; fixed in 5.4.1
- notebook (PyPI): affected all versions; fixed in 5.4.1
- notebook (PyPI): affected all versions; fixed in 5.4.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-8768/ (Markdown: https://insights.sbomify.com/CVE-2018-8768/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-8768
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-8768
- OSV: https://osv.dev/vulnerability/CVE-2018-8768

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-8768/
Summaries are generated and may contain mistakes; the official description above is the record.