Advisory record · GHSA-jwrc-gm9j-263p

JupyterLab: Command link trust prompt in JupyterLab can trust a document other than the one clicked

CVSS 4.2 MediumEPSS 0.0014 · 3rd percentile

Published by the GitHub Advisory Database at 15 Oct 2026, 20:22 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
jupyterlabPyPI>=4.6.0, <4.6.4 || >=4.5.7, <4.5.114.6.4, 4.5.11
notebookPyPI>=7.5.6, <7.6.37.6.3
jupyterlite-corePyPI>=0.7.5, <0.8.40.8.4
Identifiers
GHSA-jwrc-gm9j-263p · CVE-2026-102832
Weakness (CWE)
CWE-367 · CWE-863
Published
15 Oct 2026
Updated
15 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

JupyterLab versions 4.5.7 through 4.5.10 and 4.6.0 through 4.6.3 are affected, along with notebook 7.5.6 through 7.6.2 and jupyterlite-core 0.7.5 through 0.8.3. When a user clicks a command link in an untrusted Markdown file or notebook and chooses Trust, the trust may be applied to a different document that became current while the prompt was open, so that document's buttons later run without a prompt. Upgrade jupyterlab to 4.5.11 or 4.6.4, notebook to 7.6.3, or jupyterlite-core to 0.8.4. Choosing Run Once instead of Trust avoids the problem until upgrading.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
4.2 Medium 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0014, the 3rd percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:08 UTC First seen by agentprime
  2. 31 Oct 2026, 14:08 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.