CVE-2015-6938 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in notebook. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for notebook — see the affected versions and patch details below.
Improper Neutralization of Input During Web Page Generation in Jupyter Notebook
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
notebook🐍ipythonReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Cross-site scripting (XSS) vulnerability in the file browser in notebook/notebookapp.py in IPython Notebook before 3.2.2 and Jupyter Notebook 4.0.x before 4.0.5 allows remote attackers to inject arbitrary web script or HTML via a folder name. NOTE: this was originally reported as a cross-site request forgery (CSRF) vulnerability, but this may be inaccurate.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | notebook | ≥ 4.0.0&&< 4.0.5 | 4.0.5pip install --upgrade 'notebook==4.0.5' |
| 🐍PyPI | ipython | all versions | 3.2.2pip install --upgrade 'ipython==3.2.2' |
Affected Products
fedorafedoraprojectnotebookipythonnotebookjupyteropensuseopensuseResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for notebook, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update notebook to 4.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-6938 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2015-6938 in your dependencies?
Find it across PyPI, including transitive dependencies.