CVE-2021-41134

Stored XSS in Jupyter nbdime

MEDIUM

5.4

CVSS Score

Published: November 3, 2021 at 05:50 PM UTC

Updated: June 17, 2026 at 04:07 AM UTC

2 products affected across 1 vendorNbdime JupyterlabNbdime

Using nbdime by jupyter?

Get instant alerts when new vulnerabilities affect nbdime - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.4

Exploit prediction

EPSS 0.7%

Description

nbdime provides tools for diffing and merging of Jupyter Notebooks. In affected versions a stored cross-site scripting (XSS) issue exists within the Jupyter-owned nbdime project. It appears that when reading the file name and path from disk, the extension does not sanitize the string it constructs before returning it to be displayed. The diffNotebookCheckpoint function within nbdime causes this issue. When attempting to display the name of the local notebook (diffNotebookCheckpoint), nbdime appears to simply append .ipynb to the name of the input file. The NbdimeWidget is then created, and the base string is passed through to the request API function. From there, the frontend simply renders the HTML tag and anything along with it. Users are advised to patch to the most recent version of the affected product.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Nbdime · Jupyterpypi

95%

v < 1.0.1v < 1.1.1v < 2.1.1v < 3.1.1v < 5.0.2v < 6.1.21.0.0 ≤ v < 1.1.12.0.0 ≤ v < 2.1.13.0.0 ≤ v ≤ 3.1.15.0.0 ≤ v < 5.0.26.0.0 ≤ v < 6.1.2

Affected range stops below 1.0.1, so it looks safe — our inference, not a vendor statement

Affected range stops below 1.1.1, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.1.1, so it looks safe — our inference, not a vendor statement

Affected range stops below 3.1.1, so it looks safe — our inference, not a vendor statement

Affected range stops below 5.0.2, so it looks safe — our inference, not a vendor statement

Affected range stops below 6.1.2, so it looks safe — our inference, not a vendor statement

Nbdime Jupyterlab · Jupyternpm

95%

1.0.0 ≤ v < 1.0.12.0.0 ≤ v < 2.1.1

Affected range stops below 1.0.1, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.1.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

https://github.com/jupyter/nbdime/commit/e44a5cc7677f24b45ebafc756db49058c2f750ea

References (2)

x_refsource_MISCPatchThird Party Advisory

Source: [email protected]

https://github.com/jupyter/nbdime/commit/e44a5cc7677f24b45ebafc756db49058c2f750ea

x_refsource_CONFIRMThird Party Advisory

Source: [email protected]

https://github.com/jupyter/nbdime/security/advisories/GHSA-p6rw-44q7-3fw4

CVSS

5.4MEDIUM[email protected]

Attack Vector: NETWORK
Complexity: LOW
Privileges: LOW
User Interaction: REQUIRED
Scope: CHANGED
Confidentiality: LOW
Integrity: LOW
Availability: NONE

Vector?

Quick Info

StatusMODIFIED

CWE

CWE-79

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card