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. Specifically, invalid HTML is 'fixed' by jQuery after sanitization, making it dangerous.

Published: 2018-03-18 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2018-8768 is rated Moderate Risk (53.6/100): CVSS High severity, with medium exploitation likelihood (EPSS 1.10%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2018-8768

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.12% 1.10% +0.98%
2 2025-11-21 0.28% 0.12% -0.17%
3 2025-11-18 — 0.28% —

Full EPSS history (8 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2018-8768

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.8 3.0 HIGH
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 [email protected]
6.8 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.6 6.4 [email protected]

Weakness enumeration for CVE-2018-8768

GitHub Security Advisory for CVE-2018-8768

GHSA-6cwv-x26c-w2q4 · Severity: high · Ecosystem: pip — Jupyter Notebook file bypasses sanitization, executes JavaScript

OS Trackers for CVE-2018-8768

vendor priority summary link
debian not yet assigned CVE-2018-8768 not yet assigned priority: Debian including 2 source packages (ipython, jupyter-notebook), 10 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 10. https://security-tracker.debian.org/tracker/CVE-2018-8768
ubuntu medium CVE-2018-8768 medium priority: Ubuntu including 2 source packages (ipython, jupyter-notebook), 28 status rows across 14 suites (artful, bionic, cosmic, disco, eoan, focal, groovy, hirsute, impish, jammy, kinetic, trusty, upstream, xenial): not-affected 21, released 3, DNE 2, ignored 2. https://ubuntu.com/security/CVE-2018-8768

Affected software / configurations for CVE-2018-8768

Vendor Product Version Raw CPE
jupyter notebook < 5.4.1 cpe:2.3:a:jupyter:notebook:*:*:*:*:*:*:*:*

References for CVE-2018-8768

cvelogic Threat Intelligence