cve.bz

CVE-2026-102832 jupyterlab: Incorrect Authorization

4.2 mediumEPSS 0.1%Fix available

Medium (4.2) in jupyterlab. EPSS 0.1% estimated probability of exploitation activity in the next 30 days. Fixed in jupyterlab 4.5.11, 4.6.4.

On this page
JupyterLab is an extensible environment for interactive and reproducible computing, based on the Jupyter Notebook Architecture. From 4.5.7 until 4.5.11 and 4.6.4, the markdownviewer:trust and notebook:trust command-link handlers use tracker.currentWidget to resolve the current Markdown viewer or notebook when the user answers rather than retaining the document whose command button was clicked. If another document becomes current while the prompt is open and the user chooses Trust, JupyterLab marks the second document trusted while leaving the clicked document untrusted. Later command buttons in the incorrectly trusted document run without a prompt, and trusting a notebook marks all cells trusted, saves unsaved edits, and persists the server signature to disk. Applications that bundle JupyterLab, including affected Notebook and JupyterLite releases, inherit the behavior. This issue is fixed in versions 4.5.11 and 4.6.4.

Severity

CVSS 3.1

4.2 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 4th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition
CWE-863 Incorrect Authorization
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • jupyterlab (PyPI): fixed in 4.6.4, 4.5.11
  • notebook (PyPI): fixed in 7.6.3
  • jupyterlite-core (PyPI): fixed in 0.8.4

Ask an AI about this CVE

Show the promptExplain CVE-2026-102832 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-102832?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-102832?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-102832 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
jupyterlab>= 4.5.7, < 4.5.11
jupyterlab>= 4.6.0, < 4.6.4
jupyterlab jupyterlite-core>= 0.7.5, < 0.8.4
jupyterlab notebook>= 7.5.6, < 7.6.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-jwrc-gm9j-263pPyPIjupyterlab>=4.6.0 <4.6.44.6.4
GHSA-jwrc-gm9j-263pPyPIjupyterlab>=4.5.7 <4.5.114.5.11
GHSA-jwrc-gm9j-263pPyPInotebook>=7.5.6 <7.6.37.6.3
GHSA-jwrc-gm9j-263pPyPIjupyterlite-core>=0.7.5 <0.8.40.8.4

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu26.04:LTS, 26.10jupyterlabno fix listedUBUNTU-CVE-2026-102832

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A MODERATE severity vulnerability was found in JupyterLab, which is bundled in Red Hat OpenShift AI (RHOAI) workbench, notebook, and training container images. When a trust confirmation prompt is open, the markdownviewer:trust and notebook:trust command-link handlers resolve the document to trust from the currently active widget rather than the document whose command button was clicked. If the user switches to a different document while the prompt is open and then chooses Trust, JupyterLab marks the newly focused document as trusted while leaving the clicked document untrusted. An attacker could exploit this by convincing a user to open an untrusted notebook that unintentionally receives trusted status, allowing commands embedded in Markdown files or notebook outputs to run without further prompts; trusting a notebook also marks all of its cells trusted and persists the trust state. Exploitation requires no privileges but does require user interaction and a specific sequence of actions, which is reflected in the CVSS 3.1 score of 4.2 (AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N); this matches the upstream severity assessment. Because the impact is MODERATE and the CVSS score is below 7.0, Red Hat has deferred the fix for the affected RHOAI container images, as trackers are not filed for MODERATE severity flaws without a higher CVSS score. The residual risk is limited by the high attack complexity and the required user interaction, but a successful attack could allow embedded commands in an attacker-supplied document to execute in the user's session with low confidentiality and integrity impact.

Red Hat's mitigation

Upstream documents the following workarounds for users unable to update immediately, while advising that this issue be treated as defense-in-depth and updated at the earliest opportunity:

1. Disable the command linker by setting "@jupyterlab/apputils-extension:sanitizer": {"allowCommandLinker": false} in the JupyterLab page settings. This removes the ability to execute frontend commands from Markdown files and notebook outputs altogether; buttons in those documents then do nothing when clicked, documentation and extensions that use command links for navigation stop working, and the setting applies to every document, not only untrusted ones.

2. If disabling the command linker is not desirable, users should choose "Run Once" rather than "Trust" when the prompt appears; the command runs but no document is marked as trusted, so no document can be trusted in error.

ProductPackageStateAdvisory
Red Hat OpenShift AI (RHOAI)rhoai/odh-feature-server-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-th06-cpu-torch210-py312-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-th06-cpu-torch291-py312-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-th06-cuda130-torch210-py312-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-th06-cuda130-torch291-py312-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-th06-rocm64-torch291-py312-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-th-torch-cpu-py312-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-th-torch-cuda-py312-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-th-torch-rocm-py312-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-datascience-cpu-py312-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-minimal-cpu-py312-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-minimal-cuda-py312-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-minimal-rocm-py312-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-pytorch-cuda-py312-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-pytorch-llmcompressor-cuda-py312-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-pytorch-rocm-py312-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-tensorflow-cuda-py312-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-tensorflow-rocm-py312-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-102832.

Attack patterns (CAPEC)

  • CAPEC-27 Leveraging Race Conditions via Symbolic Links Likelihood: Medium · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON