Skip to content
Fencer Intel
high 7.8

CVE-2018-8768 json

Jupyter Notebook file bypasses sanitization, executes JavaScript

published 2018-03-18 8 y ago modified 2026-06-17 4 mo ago also GHSA-6cwv-x26c-w2q4 , PYSEC-2018-57 , EUVD-2018-0106

cvss
7.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 63%
public exploits
0
none known

Summary

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.

Patch / fix

  • pypi notebook 5.4.1
  • jupyter notebook 5.4.1
  • ipython Debian 14, Debian 13, Debian 12 5.1.0-2
  • jupyter-notebook Debian 14, Debian 13, Debian 12 5.4.1-1

debian advisories DEBIAN-CVE-2018-8768

  • ipython Ubuntu Pro 16.04 LTS 2.4.1-1ubuntu0.1~esm2

ubuntu advisories UBUNTU-CVE-2018-8768

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-8768 updated cvss 6.1

python-notebook: Input sanitization bypass allows for execution of JavaScript via crafted notebook file

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.00% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 7.8 CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P
GitHub 3.0 7.8 CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi notebook
<5.4.1
5.4.1

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.