https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 01 Oct 2026 12:31:11 +0000 https://db.gcve.eu/vuln/cve-2026-35397 <p><strong>Affected:</strong> jupyter-server jupyter_server, Red Hat Migration Toolkit for Applications 8.2, Red Hat OpenShift AI 3.4, Red Hat OpenShift AI (RHOAI)</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> jupyter-server jupyter_server, Red Hat Migration Toolkit for Applications 8.2, Red Hat OpenShift AI 3.4, Red Hat OpenShift AI (RHOAI)</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://db.gcve.eu/vuln/cve-2026-35397