https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 14:15:39 +0000 https://cve.radiocsirt.org/vuln/bit-jupyterlab-2026-73417 <p><strong>Affected:</strong> Bitnami: jupyterlab</p> <p>jupyterlab is an extensible environment for interactive and reproducible computing, based on the Jupyter Notebook Architecture. From 3.3.0 until 4.5.10 and 4.6.2, JupyterLab allows notebook settings to be shared and applied through an overrides.json file using the Import button in the Settings Editor. In packages/notebook-extension/schema/tracker.json and packages/notebook-extension/src/index.ts, the sideBySideLeftMarginOverride and sideBySideRightMarginOverride settings are not properly validated before being inserted into style content, allowing a crafted settings file to contain instructions that execute as code instead of only changing display preferences. A user can import the malicious file, or an attacker with access to a shared settings location can plant an overrides.json that is applied automatically. The embedded code runs with the affected user&#39;s access and can read or modify notebooks and files and run code through the notebook server, including on a connected kernel. This issue is fixed in versions 4.5.10 and 4.6.2.</p> <p><strong>Affected:</strong> Bitnami: jupyterlab</p> <p>jupyterlab is an extensible environment for interactive and reproducible computing, based on the Jupyter Notebook Architecture. From 3.3.0 until 4.5.10 and 4.6.2, JupyterLab allows notebook settings to be shared and applied through an overrides.json file using the Import button in the Settings Editor. In packages/notebook-extension/schema/tracker.json and packages/notebook-extension/src/index.ts, the sideBySideLeftMarginOverride and sideBySideRightMarginOverride settings are not properly validated before being inserted into style content, allowing a crafted settings file to contain instructions that execute as code instead of only changing display preferences. A user can import the malicious file, or an attacker with access to a shared settings location can plant an overrides.json that is applied automatically. The embedded code runs with the affected user&#39;s access and can read or modify notebooks and files and run code through the notebook server, including on a connected kernel. This issue is fixed in versions 4.5.10 and 4.6.2.</p> https://cve.radiocsirt.org/vuln/bit-jupyterlab-2026-73417 https://cve.radiocsirt.org/vuln/brew-jupyterlab-cve-2026-73417 <p><strong>Affected:</strong> Homebrew: jupyterlab</p> <p>JupyterLab 4.5+ allows notebook settings to be shared and applied through an `overrides.json` file using the `Import` button in the Settings Editor.</p> <p>Certain notebook display settings were not properly validated before being applied. As a result, a crafted settings file could contain hidden instructions that run as code inside JupyterLab when imported, instead of only changing a display preference.</p> <p>Because importing a settings file appears harmless, a user could import a file shared by another party without realizing it could do more. On multi-tenant file systems without proper permission control, another user could plant a malicious `overrides.json`.</p> <p>&gt; CVE assignment pending, GitHub CNA is experiencing severe backlog</p> <p>### Impact</p> <p>When a malicious settings file is applied, the embedded code runs with the same access as the affected user. This could allow an attacker to read or modify that user&#39;s notebooks and files, and to run code on the user&#39;s behalf through the notebook server, including on any connected kernel.</p> <p>#### User Interaction vs Privileges Required</p> <p>##### Write access to a loaded settings location</p> <p>If an attacker can write to a directory JupyterLab loads settings from (e.g. on shared or multi-tenant file system), they could place a crafted `overrides.json` that is applied to another user automatically at startup. This requires high privilages but no action by the victim.</p> <p>##### User-imported settings file</p> <p>A user can import a crafted `overrides.json` through t…</p> <p><strong>Affected:</strong> Homebrew: jupyterlab</p> <p>JupyterLab 4.5+ allows notebook settings to be shared and applied through an `overrides.json` file using the `Import` button in the Settings Editor.</p> <p>Certain notebook display settings were not properly validated before being applied. As a result, a crafted settings file could contain hidden instructions that run as code inside JupyterLab when imported, instead of only changing a display preference.</p> <p>Because importing a settings file appears harmless, a user could import a file shared by another party without realizing it could do more. On multi-tenant file systems without proper permission control, another user could plant a malicious `overrides.json`.</p> <p>&gt; CVE assignment pending, GitHub CNA is experiencing severe backlog</p> <p>### Impact</p> <p>When a malicious settings file is applied, the embedded code runs with the same access as the affected user. This could allow an attacker to read or modify that user&#39;s notebooks and files, and to run code on the user&#39;s behalf through the notebook server, including on any connected kernel.</p> <p>#### User Interaction vs Privileges Required</p> <p>##### Write access to a loaded settings location</p> <p>If an attacker can write to a directory JupyterLab loads settings from (e.g. on shared or multi-tenant file system), they could place a crafted `overrides.json` that is applied to another user automatically at startup. This requires high privilages but no action by the victim.</p> <p>##### User-imported settings file</p> <p>A user can import a crafted `overrides.json` through t…</p> https://cve.radiocsirt.org/vuln/brew-jupyterlab-cve-2026-73417 https://cve.radiocsirt.org/vuln/euvd-2026-352491 EUVD-2026-352491 https://cve.radiocsirt.org/vuln/euvd-2026-352491 https://cve.radiocsirt.org/vuln/fkie_cve-2026-73417 <p>jupyterlab is an extensible environment for interactive and reproducible computing, based on the Jupyter Notebook Architecture. From 3.3.0 until 4.5.10 and 4.6.2, JupyterLab allows notebook settings to be shared and applied through an overrides.json file using the Import button in the Settings Editor. In packages/notebook-extension/schema/tracker.json and packages/notebook-extension/src/index.ts, the sideBySideLeftMarginOverride and sideBySideRightMarginOverride settings are not properly validated before being inserted into style content, allowing a crafted settings file to contain instructions that execute as code instead of only changing display preferences. A user can import the malicious file, or an attacker with access to a shared settings location can plant an overrides.json that is applied automatically. The embedded code runs with the affected user&#39;s access and can read or modify notebooks and files and run code through the notebook server, including on a connected kernel. This issue is fixed in versions 4.5.10 and 4.6.2.</p> <p>jupyterlab is an extensible environment for interactive and reproducible computing, based on the Jupyter Notebook Architecture. From 3.3.0 until 4.5.10 and 4.6.2, JupyterLab allows notebook settings to be shared and applied through an overrides.json file using the Import button in the Settings Editor. In packages/notebook-extension/schema/tracker.json and packages/notebook-extension/src/index.ts, the sideBySideLeftMarginOverride and sideBySideRightMarginOverride settings are not properly validated before being inserted into style content, allowing a crafted settings file to contain instructions that execute as code instead of only changing display preferences. A user can import the malicious file, or an attacker with access to a shared settings location can plant an overrides.json that is applied automatically. The embedded code runs with the affected user&#39;s access and can read or modify notebooks and files and run code through the notebook server, including on a connected kernel. This issue is fixed in versions 4.5.10 and 4.6.2.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-73417 https://cve.radiocsirt.org/vuln/ghsa-pppj-hq3g-57pj <p><strong>Affected:</strong> PyPI: jupyterlab</p> <p>JupyterLab 4.5+ allows notebook settings to be shared and applied through an `overrides.json` file using the `Import` button in the Settings Editor.</p> <p>Certain notebook display settings were not properly validated before being applied. As a result, a crafted settings file could contain hidden instructions that run as code inside JupyterLab when imported, instead of only changing a display preference.</p> <p>Because importing a settings file appears harmless, a user could import a file shared by another party without realizing it could do more. On multi-tenant file systems without proper permission control, another user could plant a malicious `overrides.json`.</p> <p>&gt; CVE assignment pending, GitHub CNA is experiencing severe backlog</p> <p>### Impact</p> <p>When a malicious settings file is applied, the embedded code runs with the same access as the affected user. This could allow an attacker to read or modify that user&#39;s notebooks and files, and to run code on the user&#39;s behalf through the notebook server, including on any connected kernel.</p> <p>#### User Interaction vs Privileges Required</p> <p>##### Write access to a loaded settings location</p> <p>If an attacker can write to a directory JupyterLab loads settings from (e.g. on shared or multi-tenant file system), they could place a crafted `overrides.json` that is applied to another user automatically at startup. This requires high privilages but no action by the victim.</p> <p>##### User-imported settings file</p> <p>A user can import a crafted `overrides.json` through t…</p> <p><strong>Affected:</strong> PyPI: jupyterlab</p> <p>JupyterLab 4.5+ allows notebook settings to be shared and applied through an `overrides.json` file using the `Import` button in the Settings Editor.</p> <p>Certain notebook display settings were not properly validated before being applied. As a result, a crafted settings file could contain hidden instructions that run as code inside JupyterLab when imported, instead of only changing a display preference.</p> <p>Because importing a settings file appears harmless, a user could import a file shared by another party without realizing it could do more. On multi-tenant file systems without proper permission control, another user could plant a malicious `overrides.json`.</p> <p>&gt; CVE assignment pending, GitHub CNA is experiencing severe backlog</p> <p>### Impact</p> <p>When a malicious settings file is applied, the embedded code runs with the same access as the affected user. This could allow an attacker to read or modify that user&#39;s notebooks and files, and to run code on the user&#39;s behalf through the notebook server, including on any connected kernel.</p> <p>#### User Interaction vs Privileges Required</p> <p>##### Write access to a loaded settings location</p> <p>If an attacker can write to a directory JupyterLab loads settings from (e.g. on shared or multi-tenant file system), they could place a crafted `overrides.json` that is applied to another user automatically at startup. This requires high privilages but no action by the victim.</p> <p>##### User-imported settings file</p> <p>A user can import a crafted `overrides.json` through t…</p> https://cve.radiocsirt.org/vuln/ghsa-pppj-hq3g-57pj https://cve.radiocsirt.org/vuln/opensuse-su-2026:11634-1 <p>jupyter-jupyterlab-4.5.10-1.1 on GA media</p> <p>jupyter-jupyterlab-4.5.10-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:11634-1 https://cve.radiocsirt.org/vuln/pysec-2026-3672 <p><strong>Affected:</strong> PyPI: jupyterlab</p> <p>JupyterLab 4.5+ allows notebook settings to be shared and applied through an `overrides.json` file using the `Import` button in the Settings Editor.</p> <p>Certain notebook display settings were not properly validated before being applied. As a result, a crafted settings file could contain hidden instructions that run as code inside JupyterLab when imported, instead of only changing a display preference.</p> <p>Because importing a settings file appears harmless, a user could import a file shared by another party without realizing it could do more. On multi-tenant file systems without proper permission control, another user could plant a malicious `overrides.json`.</p> <p>&gt; CVE assignment pending, GitHub CNA is experiencing severe backlog</p> <p>### Impact</p> <p>When a malicious settings file is applied, the embedded code runs with the same access as the affected user. This could allow an attacker to read or modify that user&#39;s notebooks and files, and to run code on the user&#39;s behalf through the notebook server, including on any connected kernel.</p> <p>#### User Interaction vs Privileges Required</p> <p>##### Write access to a loaded settings location</p> <p>If an attacker can write to a directory JupyterLab loads settings from (e.g. on shared or multi-tenant file system), they could place a crafted `overrides.json` that is applied to another user automatically at startup. This requires high privilages but no action by the victim.</p> <p>##### User-imported settings file</p> <p>A user can import a crafted `overrides.json` through t…</p> <p><strong>Affected:</strong> PyPI: jupyterlab</p> <p>JupyterLab 4.5+ allows notebook settings to be shared and applied through an `overrides.json` file using the `Import` button in the Settings Editor.</p> <p>Certain notebook display settings were not properly validated before being applied. As a result, a crafted settings file could contain hidden instructions that run as code inside JupyterLab when imported, instead of only changing a display preference.</p> <p>Because importing a settings file appears harmless, a user could import a file shared by another party without realizing it could do more. On multi-tenant file systems without proper permission control, another user could plant a malicious `overrides.json`.</p> <p>&gt; CVE assignment pending, GitHub CNA is experiencing severe backlog</p> <p>### Impact</p> <p>When a malicious settings file is applied, the embedded code runs with the same access as the affected user. This could allow an attacker to read or modify that user&#39;s notebooks and files, and to run code on the user&#39;s behalf through the notebook server, including on any connected kernel.</p> <p>#### User Interaction vs Privileges Required</p> <p>##### Write access to a loaded settings location</p> <p>If an attacker can write to a directory JupyterLab loads settings from (e.g. on shared or multi-tenant file system), they could place a crafted `overrides.json` that is applied to another user automatically at startup. This requires high privilages but no action by the victim.</p> <p>##### User-imported settings file</p> <p>A user can import a crafted `overrides.json` through t…</p> https://cve.radiocsirt.org/vuln/pysec-2026-3672 https://cve.radiocsirt.org/vuln/rhsa-2026:65126 <p>crypto/x509: golang: Denial of Service due to excessive resource consumption via crafted certificate org.codehaus.plexus:plexus-utils: Plexus-utils: Directory Traversal in extractFile method path-to-regexp: path-to-regexp: Denial of Service via crafted regular expressions undici: undici: Information disclosure and data integrity issues due to incorrect Socks5ProxyAgent connection routing org.eclipse.parsson/parsson: Eclipse Parsson: Denial of Service via uncontrolled resource consumption in JSON parsing undici: undici: Man-in-the-Middle attack via ignored TLS options with SOCKS5 proxy undici: undici: Denial of Service due to unbounded memory growth via WebSocket frames nltk: NLTK: Information disclosure via path traversal vulnerability brace-expansion: Brace-expansion: Denial of Service due to exponential-time complexity vertx-core: Eclipse Vert.x: Information disclosure via improper handling of HTTP 30x redirects guardrails-detectors: guardrails-detectors: Unauthenticated Regular-Expression Denial of Service (ReDoS) via detector_params.regex guardrails-detectors: guardrails-detectors: SSRF and local file read via user-supplied XML Schema (xml-with-schema:) trustyai-service-operator: trustyai-service-operator: TAS internal Service bypasses kube-rbac-proxy, exposing unauthenticated Quarkus API cluster-wide odh-dashboard: odh-dashboard: Backend port 8080 trusts x-forwarded-access-token without origin validation data-science-pipelines-operator: DSPO: Operator ClusterRole grants…</p> <p>crypto/x509: golang: Denial of Service due to excessive resource consumption via crafted certificate org.codehaus.plexus:plexus-utils: Plexus-utils: Directory Traversal in extractFile method path-to-regexp: path-to-regexp: Denial of Service via crafted regular expressions undici: undici: Information disclosure and data integrity issues due to incorrect Socks5ProxyAgent connection routing org.eclipse.parsson/parsson: Eclipse Parsson: Denial of Service via uncontrolled resource consumption in JSON parsing undici: undici: Man-in-the-Middle attack via ignored TLS options with SOCKS5 proxy undici: undici: Denial of Service due to unbounded memory growth via WebSocket frames nltk: NLTK: Information disclosure via path traversal vulnerability brace-expansion: Brace-expansion: Denial of Service due to exponential-time complexity vertx-core: Eclipse Vert.x: Information disclosure via improper handling of HTTP 30x redirects guardrails-detectors: guardrails-detectors: Unauthenticated Regular-Expression Denial of Service (ReDoS) via detector_params.regex guardrails-detectors: guardrails-detectors: SSRF and local file read via user-supplied XML Schema (xml-with-schema:) trustyai-service-operator: trustyai-service-operator: TAS internal Service bypasses kube-rbac-proxy, exposing unauthenticated Quarkus API cluster-wide odh-dashboard: odh-dashboard: Backend port 8080 trusts x-forwarded-access-token without origin validation data-science-pipelines-operator: DSPO: Operator ClusterRole grants…</p> https://cve.radiocsirt.org/vuln/rhsa-2026:65126 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-73417 <p><strong>Affected:</strong> Ubuntu:26.04:LTS: jupyterlab</p> <p>jupyterlab is an extensible environment for interactive and reproducible computing, based on the Jupyter Notebook Architecture. From 3.3.0 until 4.5.10 and 4.6.2, JupyterLab allows notebook settings to be shared and applied through an overrides.json file using the Import button in the Settings Editor. In packages/notebook-extension/schema/tracker.json and packages/notebook-extension/src/index.ts, the sideBySideLeftMarginOverride and sideBySideRightMarginOverride settings are not properly validated before being inserted into style content, allowing a crafted settings file to contain instructions that execute as code instead of only changing display preferences. A user can import the malicious file, or an attacker with access to a shared settings location can plant an overrides.json that is applied automatically. The embedded code runs with the affected user&#39;s access and can read or modify notebooks and files and run code through the notebook server, including on a connected kernel. This issue is fixed in versions 4.5.10 and 4.6.2.</p> <p><strong>Affected:</strong> Ubuntu:26.04:LTS: jupyterlab</p> <p>jupyterlab is an extensible environment for interactive and reproducible computing, based on the Jupyter Notebook Architecture. From 3.3.0 until 4.5.10 and 4.6.2, JupyterLab allows notebook settings to be shared and applied through an overrides.json file using the Import button in the Settings Editor. In packages/notebook-extension/schema/tracker.json and packages/notebook-extension/src/index.ts, the sideBySideLeftMarginOverride and sideBySideRightMarginOverride settings are not properly validated before being inserted into style content, allowing a crafted settings file to contain instructions that execute as code instead of only changing display preferences. A user can import the malicious file, or an attacker with access to a shared settings location can plant an overrides.json that is applied automatically. The embedded code runs with the affected user&#39;s access and can read or modify notebooks and files and run code through the notebook server, including on a connected kernel. This issue is fixed in versions 4.5.10 and 4.6.2.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-73417