CVE-2018-19351

Jupyter Notebook before 5.7.1 allows XSS via an untrusted notebook because nbconvert responses are considered to have the same origin as the notebook server. In other words, nbconvert endpoints can execute JavaScript with access to the server API. In notebook/nbconvert/handlers.py, NbconvertFileHandler and NbconvertPostHandler do not set a Content Security Policy to prevent this.

Published: 2018-11-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-19351 is rated Moderate Risk (43/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.31%). 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-19351

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 2025-11-21 0.40% 0.31% -0.09%
2 2025-11-18 0.34% 0.40% +0.05%
3 2025-09-11 — 0.34% —

Full EPSS history (11 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.1 3.0 MEDIUM
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
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:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 2.7 [email protected]
4.3 2.0 MEDIUM
AV:N/AC:M/Au:N/C:N/I:P/A:N 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:N)
No confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:N)
No availability impact.
 8.6 2.9 [email protected]

Weakness enumeration for CVE-2018-19351

GitHub Security Advisory for CVE-2018-19351

GHSA-49qr-xh3w-h436 · Severity: medium · Ecosystem: pip — Jupyter Notebook XSS via untrusted notebooks

OS Trackers for CVE-2018-19351

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

Affected software / configurations for CVE-2018-19351

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

References for CVE-2018-19351

cvelogic Threat Intelligence