https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 15:26:12 +0000 https://cve.radiocsirt.org/vuln/brew-jupyterlab-cve-2026-35397 <p><strong>Affected:</strong> Homebrew: jupyterlab</p> <p>### Summary</p> <p>Jupyter Server &lt;=2.17.0 can access directories sibling to the root directory, if it starts with the root dir&#39;s name.</p> <p>### PoC</p> <p>Minimal:</p> <p>``` . ├── test/ &lt;- root directory. │ └── test.txt └── testtest/ └── secret.txt &lt;- file to exfiltrate that we should not be able to access via API ```</p> <p>```bash HOST=&#34;http://localhost:8888&#34; TOKEN=&#34;&#34; SIBLING=&#34;testtest&#34; TARGET=&#34;secret.txt&#34;</p> <p>curl -s -X POST \ &#34;$HOST/api/contents/%2e%2e/$SIBLING/$TARGET/checkpoints&#34; \ -H &#34;Authorization: token $TOKEN&#34; ```</p> <p>Full PoC by @stef41: https://gist.github.com/Yann-P/66d4982a965dee8fcb8dd89db29e7006</p> <p>### Impact</p> <p>It is possible for an authenticated user to access content outside the server&#39;s `root_dir` in siblings directories sharing the same prefix as the `root_dir`. The attacker can escalate access, reading, writing, and deleting from sibling directories.</p> <p>This can have a tangible impact for deployments using predictable naming scheme with multi-tenant server, for example `user1`, `user2`, `user3`, ..., `user10` etc, as `user1` could access and modify files of all `user10` - `user19` and higher.</p> <p>In a hypothetical system where users can choose a name of their folder, an attacker could choose a single-letter username to gain access to a significant number of sibling directories.</p> <p>### Workarounds</p> <p>Use folder names that do not overlap.</p> <p>### Acknowledgments</p> <p>Thank you to @stef41 for providing a useful PoC.</p> <p><strong>Affected:</strong> Homebrew: jupyterlab</p> <p>### Summary</p> <p>Jupyter Server &lt;=2.17.0 can access directories sibling to the root directory, if it starts with the root dir&#39;s name.</p> <p>### PoC</p> <p>Minimal:</p> <p>``` . ├── test/ &lt;- root directory. │ └── test.txt └── testtest/ └── secret.txt &lt;- file to exfiltrate that we should not be able to access via API ```</p> <p>```bash HOST=&#34;http://localhost:8888&#34; TOKEN=&#34;&#34; SIBLING=&#34;testtest&#34; TARGET=&#34;secret.txt&#34;</p> <p>curl -s -X POST \ &#34;$HOST/api/contents/%2e%2e/$SIBLING/$TARGET/checkpoints&#34; \ -H &#34;Authorization: token $TOKEN&#34; ```</p> <p>Full PoC by @stef41: https://gist.github.com/Yann-P/66d4982a965dee8fcb8dd89db29e7006</p> <p>### Impact</p> <p>It is possible for an authenticated user to access content outside the server&#39;s `root_dir` in siblings directories sharing the same prefix as the `root_dir`. The attacker can escalate access, reading, writing, and deleting from sibling directories.</p> <p>This can have a tangible impact for deployments using predictable naming scheme with multi-tenant server, for example `user1`, `user2`, `user3`, ..., `user10` etc, as `user1` could access and modify files of all `user10` - `user19` and higher.</p> <p>In a hypothetical system where users can choose a name of their folder, an attacker could choose a single-letter username to gain access to a significant number of sibling directories.</p> <p>### Workarounds</p> <p>Use folder names that do not overlap.</p> <p>### Acknowledgments</p> <p>Thank you to @stef41 for providing a useful PoC.</p> https://cve.radiocsirt.org/vuln/brew-jupyterlab-cve-2026-35397 https://cve.radiocsirt.org/vuln/cleanstart-2026-bf97060 <p><strong>Affected:</strong> CleanStart: tensorflow-gpu-jupyter</p> <p>Security vulnerability affects the tensorflow-gpu-jupyter package. This issue is resolved in later releases. See references for vulnerability details.</p> <p><strong>Affected:</strong> CleanStart: tensorflow-gpu-jupyter</p> <p>Security vulnerability affects the tensorflow-gpu-jupyter package. This issue is resolved in later releases. See references for vulnerability details.</p> https://cve.radiocsirt.org/vuln/cleanstart-2026-bf97060 https://cve.radiocsirt.org/vuln/euvd-2026-361085 EUVD-2026-361085 https://cve.radiocsirt.org/vuln/euvd-2026-361085 https://cve.radiocsirt.org/vuln/fkie_cve-2026-35397 <p>Jupyter Server is the backend for Jupyter web applications. In versions 2.17.0 and earlier, a path traversal vulnerability in the REST API allows an authenticated user to escape the configured root_dir and access sibling directories whose names begin with the same prefix as the root_dir. For example, with a root_dir named &#34;test&#34;, the API permits access to a sibling directory named &#34;testtest&#34; through a crafted request to the /api/contents endpoint using encoded path components. An attacker can read, write, and delete files in affected sibling directories. Multi-tenant deployments using predictable naming schemes are particularly at risk, as a user with a directory named &#34;user1&#34; could access directories for user10 through user19 and beyond. A user who can choose a single-character folder name could gain access to a significant number of sibling directories.</p> <p>Version 2.18.0 contains a fix. As a workaround, ensure folder names do not share a common prefix with any sibling directory.</p> <p>Jupyter Server is the backend for Jupyter web applications. In versions 2.17.0 and earlier, a path traversal vulnerability in the REST API allows an authenticated user to escape the configured root_dir and access sibling directories whose names begin with the same prefix as the root_dir. For example, with a root_dir named &#34;test&#34;, the API permits access to a sibling directory named &#34;testtest&#34; through a crafted request to the /api/contents endpoint using encoded path components. An attacker can read, write, and delete files in affected sibling directories. Multi-tenant deployments using predictable naming schemes are particularly at risk, as a user with a directory named &#34;user1&#34; could access directories for user10 through user19 and beyond. A user who can choose a single-character folder name could gain access to a significant number of sibling directories.</p> <p>Version 2.18.0 contains a fix. As a workaround, ensure folder names do not share a common prefix with any sibling directory.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-35397 https://cve.radiocsirt.org/vuln/ghsa-5789-5fc7-67v3 <p><strong>Affected:</strong> PyPI: jupyter-server</p> <p>### Summary</p> <p>Jupyter Server &lt;=2.17.0 can access directories sibling to the root directory, if it starts with the root dir&#39;s name.</p> <p>### PoC</p> <p>Minimal:</p> <p>``` . ├── test/ &lt;- root directory. │ └── test.txt └── testtest/ └── secret.txt &lt;- file to exfiltrate that we should not be able to access via API ```</p> <p>```bash HOST=&#34;http://localhost:8888&#34; TOKEN=&#34;&#34; SIBLING=&#34;testtest&#34; TARGET=&#34;secret.txt&#34;</p> <p>curl -s -X POST \ &#34;$HOST/api/contents/%2e%2e/$SIBLING/$TARGET/checkpoints&#34; \ -H &#34;Authorization: token $TOKEN&#34; ```</p> <p>Full PoC by @stef41: https://gist.github.com/Yann-P/66d4982a965dee8fcb8dd89db29e7006</p> <p>### Impact</p> <p>It is possible for an authenticated user to access content outside the server&#39;s `root_dir` in siblings directories sharing the same prefix as the `root_dir`. The attacker can escalate access, reading, writing, and deleting from sibling directories.</p> <p>This can have a tangible impact for deployments using predictable naming scheme with multi-tenant server, for example `user1`, `user2`, `user3`, ..., `user10` etc, as `user1` could access and modify files of all `user10` - `user19` and higher.</p> <p>In a hypothetical system where users can choose a name of their folder, an attacker could choose a single-letter username to gain access to a significant number of sibling directories.</p> <p>### Workarounds</p> <p>Use folder names that do not overlap.</p> <p>### Acknowledgments</p> <p>Thank you to @stef41 for providing a useful PoC.</p> <p><strong>Affected:</strong> PyPI: jupyter-server</p> <p>### Summary</p> <p>Jupyter Server &lt;=2.17.0 can access directories sibling to the root directory, if it starts with the root dir&#39;s name.</p> <p>### PoC</p> <p>Minimal:</p> <p>``` . ├── test/ &lt;- root directory. │ └── test.txt └── testtest/ └── secret.txt &lt;- file to exfiltrate that we should not be able to access via API ```</p> <p>```bash HOST=&#34;http://localhost:8888&#34; TOKEN=&#34;&#34; SIBLING=&#34;testtest&#34; TARGET=&#34;secret.txt&#34;</p> <p>curl -s -X POST \ &#34;$HOST/api/contents/%2e%2e/$SIBLING/$TARGET/checkpoints&#34; \ -H &#34;Authorization: token $TOKEN&#34; ```</p> <p>Full PoC by @stef41: https://gist.github.com/Yann-P/66d4982a965dee8fcb8dd89db29e7006</p> <p>### Impact</p> <p>It is possible for an authenticated user to access content outside the server&#39;s `root_dir` in siblings directories sharing the same prefix as the `root_dir`. The attacker can escalate access, reading, writing, and deleting from sibling directories.</p> <p>This can have a tangible impact for deployments using predictable naming scheme with multi-tenant server, for example `user1`, `user2`, `user3`, ..., `user10` etc, as `user1` could access and modify files of all `user10` - `user19` and higher.</p> <p>In a hypothetical system where users can choose a name of their folder, an attacker could choose a single-letter username to gain access to a significant number of sibling directories.</p> <p>### Workarounds</p> <p>Use folder names that do not overlap.</p> <p>### Acknowledgments</p> <p>Thank you to @stef41 for providing a useful PoC.</p> https://cve.radiocsirt.org/vuln/ghsa-5789-5fc7-67v3 https://cve.radiocsirt.org/vuln/oesa-2026-4080 <p><strong>Affected:</strong> openEuler:24.03-LTS-SP4: python-jupyter-server</p> <p>The backend for Jupyter web applications Security Fix(es):</p> <p>Jupyter Server is the backend for Jupyter web applications. In jupyter_server versions through 2.17.0, the next query parameter in the login flow is insufficiently validated in `LoginFormHandler._redirect_safe()`, which allows redirects to arbitrary external domains via values such as `///example.com`. An attacker can use a crafted login URL to redirect users to a malicious site and facilitate phishing attacks. This issue is fixed in version 2.18.0.(CVE-2025-61669)</p> <p>Jupyter Server is the backend for Jupyter web applications. In versions 2.17.0 and earlier, a path traversal vulnerability in the REST API allows an authenticated user to escape the configured root_dir and access sibling directories whose names begin with the same prefix as the root_dir. For example, with a root_dir named &amp;quot;test&amp;quot;, the API permits access to a sibling directory named &amp;quot;testtest&amp;quot; through a crafted request to the /api/contents endpoint using encoded path components. An attacker can read, write, and delete files in affected sibling directories. Multi-tenant deployments using predictable naming schemes are particularly at risk, as a user with a directory named &amp;quot;user1&amp;quot; could access directories for user10 through user19 and beyond. A user who can choose a single-character folder name could gain access to a significant number of sibling directories.</p> <p>Version 2.18.0 contains a fix. As a workaround, ensure folder nam…</p> <p><strong>Affected:</strong> openEuler:24.03-LTS-SP4: python-jupyter-server</p> <p>The backend for Jupyter web applications Security Fix(es):</p> <p>Jupyter Server is the backend for Jupyter web applications. In jupyter_server versions through 2.17.0, the next query parameter in the login flow is insufficiently validated in `LoginFormHandler._redirect_safe()`, which allows redirects to arbitrary external domains via values such as `///example.com`. An attacker can use a crafted login URL to redirect users to a malicious site and facilitate phishing attacks. This issue is fixed in version 2.18.0.(CVE-2025-61669)</p> <p>Jupyter Server is the backend for Jupyter web applications. In versions 2.17.0 and earlier, a path traversal vulnerability in the REST API allows an authenticated user to escape the configured root_dir and access sibling directories whose names begin with the same prefix as the root_dir. For example, with a root_dir named &amp;quot;test&amp;quot;, the API permits access to a sibling directory named &amp;quot;testtest&amp;quot; through a crafted request to the /api/contents endpoint using encoded path components. An attacker can read, write, and delete files in affected sibling directories. Multi-tenant deployments using predictable naming schemes are particularly at risk, as a user with a directory named &amp;quot;user1&amp;quot; could access directories for user10 through user19 and beyond. A user who can choose a single-character folder name could gain access to a significant number of sibling directories.</p> <p>Version 2.18.0 contains a fix. As a workaround, ensure folder nam…</p> https://cve.radiocsirt.org/vuln/oesa-2026-4080 https://cve.radiocsirt.org/vuln/opensuse-su-2026:10710-1 <p>python311-jupyter-server-2.18.1-1.1 on GA media</p> <p>python311-jupyter-server-2.18.1-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:10710-1 https://cve.radiocsirt.org/vuln/pysec-2026-68 <p><strong>Affected:</strong> PyPI: jupyter-server</p> <p>Jupyter Server is the backend for Jupyter web applications. In versions 2.17.0 and earlier, a path traversal vulnerability in the REST API allows an authenticated user to escape the configured root_dir and access sibling directories whose names begin with the same prefix as the root_dir. For example, with a root_dir named &#34;test&#34;, the API permits access to a sibling directory named &#34;testtest&#34; through a crafted request to the /api/contents endpoint using encoded path components. An attacker can read, write, and delete files in affected sibling directories. Multi-tenant deployments using predictable naming schemes are particularly at risk, as a user with a directory named &#34;user1&#34; could access directories for user10 through user19 and beyond. A user who can choose a single-character folder name could gain access to a significant number of sibling directories.</p> <p>Version 2.18.0 contains a fix. As a workaround, ensure folder names do not share a common prefix with any sibling directory.</p> <p><strong>Affected:</strong> PyPI: jupyter-server</p> <p>Jupyter Server is the backend for Jupyter web applications. In versions 2.17.0 and earlier, a path traversal vulnerability in the REST API allows an authenticated user to escape the configured root_dir and access sibling directories whose names begin with the same prefix as the root_dir. For example, with a root_dir named &#34;test&#34;, the API permits access to a sibling directory named &#34;testtest&#34; through a crafted request to the /api/contents endpoint using encoded path components. An attacker can read, write, and delete files in affected sibling directories. Multi-tenant deployments using predictable naming schemes are particularly at risk, as a user with a directory named &#34;user1&#34; could access directories for user10 through user19 and beyond. A user who can choose a single-character folder name could gain access to a significant number of sibling directories.</p> <p>Version 2.18.0 contains a fix. As a workaround, ensure folder names do not share a common prefix with any sibling directory.</p> https://cve.radiocsirt.org/vuln/pysec-2026-68 https://cve.radiocsirt.org/vuln/rhsa-2026:43038 <p>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…</p> <p>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…</p> https://cve.radiocsirt.org/vuln/rhsa-2026:43038 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-35397 <p><strong>Affected:</strong> Ubuntu:22.04:LTS: jupyter-server, Ubuntu:24.04:LTS: jupyter-server, Ubuntu:25.10: jupyter-server, Ubuntu:26.04:LTS: jupyter-server</p> <p>Jupyter Server is the backend for Jupyter web applications. In versions 2.17.0 and earlier, a path traversal vulnerability in the REST API allows an authenticated user to escape the configured root_dir and access sibling directories whose names begin with the same prefix as the root_dir. For example, with a root_dir named &#34;test&#34;, the API permits access to a sibling directory named &#34;testtest&#34; through a crafted request to the /api/contents endpoint using encoded path components. An attacker can read, write, and delete files in affected sibling directories. Multi-tenant deployments using predictable naming schemes are particularly at risk, as a user with a directory named &#34;user1&#34; could access directories for user10 through user19 and beyond. A user who can choose a single-character folder name could gain access to a significant number of sibling directories. Version 2.18.0 contains a fix. As a workaround, ensure folder names do not share a common prefix with any sibling directory.</p> <p><strong>Affected:</strong> Ubuntu:22.04:LTS: jupyter-server, Ubuntu:24.04:LTS: jupyter-server, Ubuntu:25.10: jupyter-server, Ubuntu:26.04:LTS: jupyter-server</p> <p>Jupyter Server is the backend for Jupyter web applications. In versions 2.17.0 and earlier, a path traversal vulnerability in the REST API allows an authenticated user to escape the configured root_dir and access sibling directories whose names begin with the same prefix as the root_dir. For example, with a root_dir named &#34;test&#34;, the API permits access to a sibling directory named &#34;testtest&#34; through a crafted request to the /api/contents endpoint using encoded path components. An attacker can read, write, and delete files in affected sibling directories. Multi-tenant deployments using predictable naming schemes are particularly at risk, as a user with a directory named &#34;user1&#34; could access directories for user10 through user19 and beyond. A user who can choose a single-character folder name could gain access to a significant number of sibling directories. Version 2.18.0 contains a fix. As a workaround, ensure folder names do not share a common prefix with any sibling directory.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-35397