← Search results
CVE-LINKED INVENTORY16 SECURITY RECORDS
jupyterlab
jupyterlab
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
Official registry publication history is available at jupyterlab, but registry activity is not a publisher support boundary.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-102904 | 29 Sep 2026 | jupyterlab: >= 4.0.0, < 4.5.11, >= 4.6.0, < 4.6.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-102831 | 29 Sep 2026 | jupyterlab: >= 4.5.0, < 4.5.11, >= 4.6.0, < 4.6.4; notebook: >= 7.5.0, < 7.6.3; jupyterlite-core: >= 0.7.0, < 0.8.4 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-102830 | 29 Sep 2026 | jupyterlab: >= 3.0.0, < 4.5.11, >= 4.6.0, < 4.6.4; jupyterlite-core: < 0.8.4 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-73417 | 13 Aug 2026 | jupyterlab: >= 3.3.0, < 4.5.10, >= 4.6.0, < 4.6.2 | For Red Hat OpenShift AI 2.25.11 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this errata update: https://docs.redhat.com/en/documentation/red_hat_openshift_ai/ | Update reference ↗ |
| CVE-2026-73416 | 13 Aug 2026 | jupyterlab: >= 4.5.0, < 4.5.10, >= 4.6.0, < 4.6.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-73627 | 13 Aug 2026 | jupyterlab: 4.6.0 ≤ 4.6.1, 4.1.0 ≤ 4.5.9 | For Red Hat OpenShift AI 2.25.11 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this errata update: https://docs.redhat.com/en/documentation/red_hat_openshift_ai/ | Update reference ↗ |
| CVE-2026-73626 | 13 Aug 2026 | 4.6.0 < 4.6.1; < 4.5.10 | 4.6.1; 4.5.10 | Update reference ↗ |
| CVE-2026-73415 | 12 Aug 2026 | < 4.5.10; >= 4.6.0, < 4.6.2 | For Red Hat OpenShift AI 2.25.11 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this errata update: https://docs.redhat.com/en/documentation/red_hat_openshift_ai/ | Update reference ↗ |
| CVE-2026-67338 | 1 Aug 2026 | < 4.5.9 | 4.5.9 | Update reference ↗ |
| CVE-2026-42266 | 13 May 2026 | >= 4.0.0, < 4.5.7 | Before applying this update, make sure all previously released errata relevant to your system have been applied. | Update reference ↗ |
| CVE-2026-42557 | 13 May 2026 | < 4.5.7; >= 7.0.0, < 7.5.6 | Before applying this update, make sure all previously released errata relevant to your system have been applied. | Update reference ↗ |
| CVE-2025-59842 | 26 Sep 2025 | < 4.4.8 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2024-43805 | 28 Aug 2024 | notebook: >= 7.0.0, <= 7.2.2; jupyterlab: >= 4.0.0, < 4.2.5; jupyterlab: < 3.6.8 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-22420 | 19 Jan 2024 | >=4.0.0, < 4.0.11 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2024-22421 | 19 Jan 2024 | < 3.6.7; >=4.0.0,< 4.0.11 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-32797 | 9 Aug 2021 | >= 3.1.0, < 3.1.4; >= 3.0.0, < 3.0.17; >= 2.3.0, < 2.3.2; >= 2.0.0, < 2.2.10; < 1.2.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.