<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-14T17:10:32.196240+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/cve-2021-41134</id>
    <title>CVE-2021-41134 — Stored XSS in Jupyter nbdime</title>
    <updated>2026-10-14T17:10:32.198362+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> jupyter nbdime</p>
<p>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.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2021-41134"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-p6rw-44q7-3fw4</id>
    <title>GHSA-p6rw-44q7-3fw4 — Stored XSS in Jupyter nbdime</title>
    <updated>2026-10-14T17:10:32.198445+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: nbdime, npm: nbdime, npm: nbdime-jupyterlab</p>
<p>### Impact</p>
<p>Improper handling of user controlled input caused a stored cross-site scripting (XSS) vulnerability. All previous versions of nbdime are affected.</p>
<p>### Patches</p>
<p>Security patches will be released for each of the major versions of the nbdime packages since version 1.x of the nbdime python package.</p>
<p>#### Python
- nbdime 1.x: Patched in v. 1.1.1
- nbdime 2.x: Patched in v. 2.1.1
- nbdime 3.x: Patched in v. 3.1.1</p>
<p>#### npm
- nbdime 6.x version: Patched in 6.1.2
- nbdime 5.x version: Patched in 5.0.2
- nbdime-jupyterlab 1.x version: Patched in 1.0.1
- nbdime-jupyterlab 2.x version: Patched in 2.1.1</p>
<p>### For more information
If you have any questions or comments about this advisory email us at [security@ipython.org](mailto:security@ipython.org).</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-p6rw-44q7-3fw4"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/pysec-2021-428</id>
    <title>PYSEC-2021-428</title>
    <updated>2026-10-14T17:10:32.198489+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: nbdime</p>
<p>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.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/pysec-2021-428"/>
  </entry>
</feed>
