UBUNTU-CVE-2026-73626

Source
https://ubuntu.com/security/CVE-2026-73626
Import Source
https://github.com/canonical/ubuntu-security-notices/blob/main/osv/cve/2026/UBUNTU-CVE-2026-73626.json
JSON Data
https://api.osv.dev/v1/vulns/UBUNTU-CVE-2026-73626
Upstream
Published
2026-08-14T00:00:00Z
Modified
2026-08-14T20:45:31.003948354Z
Severity
  • 0.0 (None) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:N CVSS Calculator
  • 0.0 (None) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N CVSS Calculator
  • Ubuntu - medium
Summary
[none]
Details

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 isinstallallowed 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.

References

Affected packages

Ubuntu:26.04:LTS / jupyterlab

Package

Name
jupyterlab
Purl
pkg:deb/ubuntu/jupyterlab?arch=source&distro=resolute

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected

Affected versions

4.*
4.0.11+ds1+~cs11.25.27-7
4.0.11+ds1+~cs11.25.27-8
4.0.11+ds1+~cs11.25.27-9

Ecosystem specific

{
    "binaries": [
        {
            "binary_version": "4.0.11+ds1+~cs11.25.27-9",
            "binary_name": "jupyterlab"
        }
    ]
}

Database specific

source
"https://github.com/canonical/ubuntu-security-notices/blob/main/osv/cve/2026/UBUNTU-CVE-2026-73626.json"