<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 02 Oct 2026 16:26:21 +0000</lastBuildDate>
    <item>
      <title>BREW-jupyterlab-CVE-2026-44727 — Jupyter Server: Stored XSS in `NbconvertFileHandler` / `NbconvertPostHandler` via missing `sandbox` CSP</title>
      <link>https://cve.radiocsirt.org/vuln/brew-jupyterlab-cve-2026-44727</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: jupyterlab&lt;/p&gt;
&lt;p&gt;The nbconvert HTTP handlers in jupyter_server render user-authored notebook HTML under the Jupyter origin without a sandbox directive in their `Content-Security-Policy`.&lt;/p&gt;
&lt;p&gt;Combined with `nbconvert.HTMLExporter`&amp;#39;s default non-sanitizing behavior, a notebook carrying an HTML payload in a display_data output triggers stored XSS with cookie access, full /api/* authority, and kernel RCE.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An authenticated victim who navigates to `/nbconvert/html/&amp;lt;path&amp;gt;` containing attacker-authored output can have their token exfiltrated to another domain because it is executed in the Jupyter origin.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Fixed in v2.20.0, commit [6cbee8d](https://github.com/jupyter-server/jupyter_server/commit/6cbee8d65e71abac851c4492fea987ad080580bd)&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;For deployments where editing the installed jupyter_server is impractical (containerized builds, read-only images), adding this to jupyter_server_config.py has the same effect as the patch above without touching source files:&lt;/p&gt;
&lt;p&gt;```
import jupyter_server.nbconvert.handlers as _nb&lt;/p&gt;
&lt;p&gt;def _csp(self):
    return super(type(self), self).content_security_policy + &amp;#34;; sandbox allow-scripts&amp;#34;&lt;/p&gt;
&lt;p&gt;_nb.NbconvertFileHandler.content_security_policy = property(_csp)
_nb.NbconvertPostHandler.content_security_policy = property(_csp)
```&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: jupyterlab&lt;/p&gt;
&lt;p&gt;The nbconvert HTTP handlers in jupyter_server render user-authored notebook HTML under the Jupyter origin without a sandbox directive in their `Content-Security-Policy`.&lt;/p&gt;
&lt;p&gt;Combined with `nbconvert.HTMLExporter`&amp;#39;s default non-sanitizing behavior, a notebook carrying an HTML payload in a display_data output triggers stored XSS with cookie access, full /api/* authority, and kernel RCE.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An authenticated victim who navigates to `/nbconvert/html/&amp;lt;path&amp;gt;` containing attacker-authored output can have their token exfiltrated to another domain because it is executed in the Jupyter origin.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Fixed in v2.20.0, commit [6cbee8d](https://github.com/jupyter-server/jupyter_server/commit/6cbee8d65e71abac851c4492fea987ad080580bd)&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;For deployments where editing the installed jupyter_server is impractical (containerized builds, read-only images), adding this to jupyter_server_config.py has the same effect as the patch above without touching source files:&lt;/p&gt;
&lt;p&gt;```
import jupyter_server.nbconvert.handlers as _nb&lt;/p&gt;
&lt;p&gt;def _csp(self):
    return super(type(self), self).content_security_policy + &amp;#34;; sandbox allow-scripts&amp;#34;&lt;/p&gt;
&lt;p&gt;_nb.NbconvertFileHandler.content_security_policy = property(_csp)
_nb.NbconvertPostHandler.content_security_policy = property(_csp)
```&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-jupyterlab-cve-2026-44727</guid>
    </item>
    <item>
      <title>CLEANSTART-2026-SY39659 — Security fix for CVE-2026-44727 applied in: tensorflow-gpu-jupyter 2.21.0-r8</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2026-sy39659</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: tensorflow-gpu-jupyter&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the tensorflow-gpu-jupyter package. This issue is resolved in later releases. See references for vulnerability details.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: tensorflow-gpu-jupyter&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the tensorflow-gpu-jupyter package. This issue is resolved in later releases. See references for vulnerability details.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2026-sy39659</guid>
    </item>
    <item>
      <title>EUVD-2026-361081</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-361081</link>
      <description>EUVD-2026-361081</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-361081</guid>
    </item>
    <item>
      <title>fkie_cve-2026-44727</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-44727</link>
      <description>&lt;p&gt;Jupyter Server is the backend for Jupyter web applications. Prior to 2.20, the nbconvert HTTP handlers in jupyter_server render user-authored notebook HTML under the Jupyter origin without a sandbox directive in their Content-Security-Policy. Combined with nbconvert.HTMLExporter&amp;#39;s default non-sanitizing behavior, a notebook carrying an HTML payload in a display_data output triggers stored XSS with cookie access, full /api/* authority, and kernel RCE. This vulnerability is fixed in 2.20.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Jupyter Server is the backend for Jupyter web applications. Prior to 2.20, the nbconvert HTTP handlers in jupyter_server render user-authored notebook HTML under the Jupyter origin without a sandbox directive in their Content-Security-Policy. Combined with nbconvert.HTMLExporter&amp;#39;s default non-sanitizing behavior, a notebook carrying an HTML payload in a display_data output triggers stored XSS with cookie access, full /api/* authority, and kernel RCE. This vulnerability is fixed in 2.20.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-44727</guid>
    </item>
    <item>
      <title>GHSA-fcw5-x6j4-ccmp — Jupyter Server: Stored XSS in `NbconvertFileHandler` / `NbconvertPostHandler` via missing `sandbox` CSP</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-fcw5-x6j4-ccmp</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: jupyter-server&lt;/p&gt;
&lt;p&gt;The nbconvert HTTP handlers in jupyter_server render user-authored notebook HTML under the Jupyter origin without a sandbox directive in their `Content-Security-Policy`.&lt;/p&gt;
&lt;p&gt;Combined with `nbconvert.HTMLExporter`&amp;#39;s default non-sanitizing behavior, a notebook carrying an HTML payload in a display_data output triggers stored XSS with cookie access, full /api/* authority, and kernel RCE.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An authenticated victim who navigates to `/nbconvert/html/&amp;lt;path&amp;gt;` containing attacker-authored output can have their token exfiltrated to another domain because it is executed in the Jupyter origin.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Fixed in v2.20.0, commit [6cbee8d](https://github.com/jupyter-server/jupyter_server/commit/6cbee8d65e71abac851c4492fea987ad080580bd)&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;For deployments where editing the installed jupyter_server is impractical (containerized builds, read-only images), adding this to jupyter_server_config.py has the same effect as the patch above without touching source files:&lt;/p&gt;
&lt;p&gt;```
import jupyter_server.nbconvert.handlers as _nb&lt;/p&gt;
&lt;p&gt;def _csp(self):
    return super(type(self), self).content_security_policy + &amp;#34;; sandbox allow-scripts&amp;#34;&lt;/p&gt;
&lt;p&gt;_nb.NbconvertFileHandler.content_security_policy = property(_csp)
_nb.NbconvertPostHandler.content_security_policy = property(_csp)
```&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: jupyter-server&lt;/p&gt;
&lt;p&gt;The nbconvert HTTP handlers in jupyter_server render user-authored notebook HTML under the Jupyter origin without a sandbox directive in their `Content-Security-Policy`.&lt;/p&gt;
&lt;p&gt;Combined with `nbconvert.HTMLExporter`&amp;#39;s default non-sanitizing behavior, a notebook carrying an HTML payload in a display_data output triggers stored XSS with cookie access, full /api/* authority, and kernel RCE.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An authenticated victim who navigates to `/nbconvert/html/&amp;lt;path&amp;gt;` containing attacker-authored output can have their token exfiltrated to another domain because it is executed in the Jupyter origin.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Fixed in v2.20.0, commit [6cbee8d](https://github.com/jupyter-server/jupyter_server/commit/6cbee8d65e71abac851c4492fea987ad080580bd)&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;For deployments where editing the installed jupyter_server is impractical (containerized builds, read-only images), adding this to jupyter_server_config.py has the same effect as the patch above without touching source files:&lt;/p&gt;
&lt;p&gt;```
import jupyter_server.nbconvert.handlers as _nb&lt;/p&gt;
&lt;p&gt;def _csp(self):
    return super(type(self), self).content_security_policy + &amp;#34;; sandbox allow-scripts&amp;#34;&lt;/p&gt;
&lt;p&gt;_nb.NbconvertFileHandler.content_security_policy = property(_csp)
_nb.NbconvertPostHandler.content_security_policy = property(_csp)
```&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-fcw5-x6j4-ccmp</guid>
    </item>
    <item>
      <title>OESA-2026-3954 — python-jupyter-server security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-3954</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: python-jupyter-server&lt;/p&gt;
&lt;p&gt;The backend for Jupyter web applications&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;The nbconvert HTTP handlers in jupyter_server render user-authored notebook HTML under the Jupyter origin without a sandbox directive in their `Content-Security-Policy`. Combined with `nbconvert.HTMLExporter`&amp;amp;apos;s default non-sanitizing behavior, a notebook carrying an HTML payload in a display_data output triggers stored XSS with cookie access, full /api/* authority, and kernel RCE. An authenticated victim who navigates to `/nbconvert/html/&amp;amp;lt;path&amp;amp;gt;` containing attacker-authored output can have their token exfiltrated to another domain because it is executed in the Jupyter origin.(CVE-2026-44727)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: python-jupyter-server&lt;/p&gt;
&lt;p&gt;The backend for Jupyter web applications&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;The nbconvert HTTP handlers in jupyter_server render user-authored notebook HTML under the Jupyter origin without a sandbox directive in their `Content-Security-Policy`. Combined with `nbconvert.HTMLExporter`&amp;amp;apos;s default non-sanitizing behavior, a notebook carrying an HTML payload in a display_data output triggers stored XSS with cookie access, full /api/* authority, and kernel RCE. An authenticated victim who navigates to `/nbconvert/html/&amp;amp;lt;path&amp;amp;gt;` containing attacker-authored output can have their token exfiltrated to another domain because it is executed in the Jupyter origin.(CVE-2026-44727)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-3954</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11159-1 — python311-jupyter-server-2.20.0-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:11159-1</link>
      <description>&lt;p&gt;python311-jupyter-server-2.20.0-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;python311-jupyter-server-2.20.0-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:11159-1</guid>
    </item>
    <item>
      <title>PYSEC-2026-366 — Jupyter Server: Stored XSS in `NbconvertFileHandler` / `NbconvertPostHandler` via missing `sandbox` CSP</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-366</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: jupyter-server&lt;/p&gt;
&lt;p&gt;The nbconvert HTTP handlers in jupyter_server render user-authored notebook HTML under the Jupyter origin without a sandbox directive in their `Content-Security-Policy`.&lt;/p&gt;
&lt;p&gt;Combined with `nbconvert.HTMLExporter`&amp;#39;s default non-sanitizing behavior, a notebook carrying an HTML payload in a display_data output triggers stored XSS with cookie access, full /api/* authority, and kernel RCE.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An authenticated victim who navigates to `/nbconvert/html/&amp;lt;path&amp;gt;` containing attacker-authored output can have their token exfiltrated to another domain because it is executed in the Jupyter origin.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Fixed in v2.20.0, commit [6cbee8d](https://github.com/jupyter-server/jupyter_server/commit/6cbee8d65e71abac851c4492fea987ad080580bd)&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;For deployments where editing the installed jupyter_server is impractical (containerized builds, read-only images), adding this to jupyter_server_config.py has the same effect as the patch above without touching source files:&lt;/p&gt;
&lt;p&gt;```
import jupyter_server.nbconvert.handlers as _nb&lt;/p&gt;
&lt;p&gt;def _csp(self):
    return super(type(self), self).content_security_policy + &amp;#34;; sandbox allow-scripts&amp;#34;&lt;/p&gt;
&lt;p&gt;_nb.NbconvertFileHandler.content_security_policy = property(_csp)
_nb.NbconvertPostHandler.content_security_policy = property(_csp)
```&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: jupyter-server&lt;/p&gt;
&lt;p&gt;The nbconvert HTTP handlers in jupyter_server render user-authored notebook HTML under the Jupyter origin without a sandbox directive in their `Content-Security-Policy`.&lt;/p&gt;
&lt;p&gt;Combined with `nbconvert.HTMLExporter`&amp;#39;s default non-sanitizing behavior, a notebook carrying an HTML payload in a display_data output triggers stored XSS with cookie access, full /api/* authority, and kernel RCE.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An authenticated victim who navigates to `/nbconvert/html/&amp;lt;path&amp;gt;` containing attacker-authored output can have their token exfiltrated to another domain because it is executed in the Jupyter origin.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Fixed in v2.20.0, commit [6cbee8d](https://github.com/jupyter-server/jupyter_server/commit/6cbee8d65e71abac851c4492fea987ad080580bd)&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;For deployments where editing the installed jupyter_server is impractical (containerized builds, read-only images), adding this to jupyter_server_config.py has the same effect as the patch above without touching source files:&lt;/p&gt;
&lt;p&gt;```
import jupyter_server.nbconvert.handlers as _nb&lt;/p&gt;
&lt;p&gt;def _csp(self):
    return super(type(self), self).content_security_policy + &amp;#34;; sandbox allow-scripts&amp;#34;&lt;/p&gt;
&lt;p&gt;_nb.NbconvertFileHandler.content_security_policy = property(_csp)
_nb.NbconvertPostHandler.content_security_policy = property(_csp)
```&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-366</guid>
    </item>
    <item>
      <title>RHSA-2026:43038 — Red Hat Security Advisory: Migration Toolkit for Applications</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:43038</link>
      <description>&lt;p&gt;jupyter-server: jupyter-server: Sensitive data exposure via path traversal vulnerability fast-uri: fast-uri: URI authority bypass due to improper delimiter handling fast-uri: fast-uri: Security policy bypass due to improper Unicode hostname canonicalization golang.org/x/net/html: golang.org/x/net/html: Arbitrary code execution via Cross-Site Scripting golang.org/x/net/html: golang: golang.org/x/net/html: Cross-Site Scripting via HTML parsing bypass python-dotenv: python-dotenv: Arbitrary file overwrite via symbolic link following mistune: Mistune: Regular Expression Denial of Service (ReDoS) via crafted Markdown input net: golang: Go net package: Denial of Service via long CNAME response in LookupCNAME aiohttp: AIOHTTP: Arbitrary code execution via untrusted input to CookieJar.load() jupyter-server: Jupyter Server: Unauthorized File Access via Path Traversal Vulnerability net/mail: golang: Go net/mail: Denial of Service via crafted email inputs golang.org/x/net/idna: golang: net/http: golang.org/x/net/idna: Privilege escalation via incorrect Punycode label processing jupyter-server: Jupyter Server: Cross-Origin Resource Sharing (CORS) bypass via improper Origin header validation Jupyter Notebook: JupyterLab: @jupyter-notebook/help-extension: @jupyterlab/help-extension: Jupyter Notebook and JupyterLab: Session takeover via stored cross-site scripting jupyterlab: JupyterLab: Arbitrary code execution due to improper enforcement of extension allow-list net/mail: golang: net/mail…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;jupyter-server: jupyter-server: Sensitive data exposure via path traversal vulnerability fast-uri: fast-uri: URI authority bypass due to improper delimiter handling fast-uri: fast-uri: Security policy bypass due to improper Unicode hostname canonicalization golang.org/x/net/html: golang.org/x/net/html: Arbitrary code execution via Cross-Site Scripting golang.org/x/net/html: golang: golang.org/x/net/html: Cross-Site Scripting via HTML parsing bypass python-dotenv: python-dotenv: Arbitrary file overwrite via symbolic link following mistune: Mistune: Regular Expression Denial of Service (ReDoS) via crafted Markdown input net: golang: Go net package: Denial of Service via long CNAME response in LookupCNAME aiohttp: AIOHTTP: Arbitrary code execution via untrusted input to CookieJar.load() jupyter-server: Jupyter Server: Unauthorized File Access via Path Traversal Vulnerability net/mail: golang: Go net/mail: Denial of Service via crafted email inputs golang.org/x/net/idna: golang: net/http: golang.org/x/net/idna: Privilege escalation via incorrect Punycode label processing jupyter-server: Jupyter Server: Cross-Origin Resource Sharing (CORS) bypass via improper Origin header validation Jupyter Notebook: JupyterLab: @jupyter-notebook/help-extension: @jupyterlab/help-extension: Jupyter Notebook and JupyterLab: Session takeover via stored cross-site scripting jupyterlab: JupyterLab: Arbitrary code execution due to improper enforcement of extension allow-list net/mail: golang: net/mail…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:43038</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-44727</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-44727</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: jupyter-server, Ubuntu:24.04:LTS: jupyter-server, Ubuntu:25.10: jupyter-server, Ubuntu:26.04:LTS: jupyter-server&lt;/p&gt;
&lt;p&gt;Jupyter Server is the backend for Jupyter web applications. Prior to 2.20, the nbconvert HTTP handlers in jupyter_server render user-authored notebook HTML under the Jupyter origin without a sandbox directive in their Content-Security-Policy. Combined with nbconvert.HTMLExporter&amp;#39;s default non-sanitizing behavior, a notebook carrying an HTML payload in a display_data output triggers stored XSS with cookie access, full /api/* authority, and kernel RCE. This vulnerability is fixed in 2.20.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: jupyter-server, Ubuntu:24.04:LTS: jupyter-server, Ubuntu:25.10: jupyter-server, Ubuntu:26.04:LTS: jupyter-server&lt;/p&gt;
&lt;p&gt;Jupyter Server is the backend for Jupyter web applications. Prior to 2.20, the nbconvert HTTP handlers in jupyter_server render user-authored notebook HTML under the Jupyter origin without a sandbox directive in their Content-Security-Policy. Combined with nbconvert.HTMLExporter&amp;#39;s default non-sanitizing behavior, a notebook carrying an HTML payload in a display_data output triggers stored XSS with cookie access, full /api/* authority, and kernel RCE. This vulnerability is fixed in 2.20.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-44727</guid>
    </item>
  </channel>
</rss>
