Skip to main content
No exploitation reportedFix available

CVE-2026-73626

No exploitation reported by the sources we read.

  • Published2026-08-13
  • Fixed in4.6.2 · 4.5.10
  • WeaknessCWE-284

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

JupyterLab versions >=4.6.0,<=4.6.1 and <=4.5.9 contain an allowlist/blocklist enforcement gap in PyPIExtensionManager.install(). A missing 'await' caused the is_install_allowed coroutine to never execute, so the extension allowlist/blocklist check was not enforced for direct callers of install(). The stock JupyterLab HTTP API and Extension Manager UI are not affected, as they perform a separate, correctly awaited check. The issue affects only deployments where a custom extension or downstream integration imports PyPIExtensionManager and calls install() directly with a package name influenced by untrusted input, an allowlist/blocklist is configured, the PyPI Extension Manager is enabled, and kernels and terminals are disabled or delegated to remote hosts. Fixed in JupyterLab 4.6.2 and 4.5.10.

Timeline

dates in UTC
  1. 2026-08-1312:17CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-25 09:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-73626?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-73626?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

OSV
jupyterlab
BranchAffectedFixed in
4.6≥ 4.6.0, < 4.6.24.6.2
4.5< 4.5.104.5.10
jupyterlab
BranchAffectedFixed in
4.6≥ 4.6.0, < 4.6.24.6.2
4.5< 4.5.104.5.10

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

  • CVE-2026-73626 Red Hat Product Security17 known affected

    jupyterlab: JupyterLab: Extension allowlist bypass allows unauthorized installations

    mta/mta-solution-server-rhel9 as a component of Migration Toolkit for Applications 8 · rhoai/odh-feature-server-rhel9 as a component of Red Hat OpenShift AI (RHOAI) · rhoai/odh-th06-cpu-torch210-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI) · +14 more

Full record on NVD

Fix

  1. Update jupyterlab to 4.6.2 · 4.5.10
  2. No fix available, says the vendor Red Hat Product Security CVE-2026-73626 · 16 productsFix deferred
  3. No fix planned, says the vendor Red Hat Product Security CVE-2026-73626 · 1 productOut of support scope

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • CISA-ADPSSVC decisionnone2026-08-13
  • OpenCVESSVC decisionnone—
  • CNACVSS 4.07.7read 2026-10-23
  • NVDCVSS 3.17.5read 2026-10-23
  • CNAweakness (CWE)CWE-284read 2026-10-23
  • FIRST EPSSEPSS score0.4 %2026-10-24
  • OSVaffected packages—

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS 4.0 vector
CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Published
2026-08-13
Last Modified
2026-09-09
NVD status
Awaiting Analysis

Frequently asked questions

What is CVE-2026-73626?

JupyterLab versions >=4.6.0,<=4.6.1 and <=4.5.9 contain an allowlist/blocklist enforcement gap in PyPIExtensionManager.install(). A missing 'await' caused the is_install_allowed coroutine to never execute, so the extension allowlist/blocklist check was not enforced for direct callers of install(). The stock JupyterLab HTTP API and Extension Manager UI are not affected, as they perform a separate, correctly awaited check. The issue affects only deployments where a custom extension or downstream integration imports PyPIExtensionManager and calls install() directly with a package name influenced by untrusted input, an allowlist/blocklist is configured, the PyPI Extension Manager is enabled, and kernels and terminals are disabled or delegated to remote hosts. Fixed in JupyterLab 4.6.2 and 4.5.10.

Is CVE-2026-73626 actively exploited?

Active exploitation of CVE-2026-73626 has not been confirmed. Its EPSS score was 0.4% on 2026-10-24, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-73626?

CVE-2026-73626 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H.

Running jupyterlab? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database