Answer in brief
CVE-2024-39700 records a Critical severity (CVSS 10.0) vulnerability in Remote Code Execution (RCE) vulnerability in jupyterlab extension template `update-integration-tests` GitHub Action. The current sources do not mark it as known exploited. The current feed maps jupyterlab/extension-template (generic), jupyter/extension-template (generic), jupyterlab (pypi). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 10.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps jupyterlab/extension-template (generic), jupyter/extension-template (generic), jupyterlab (pypi). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| jupyterlab/extension-templategeneric | <4.3.3 | 4.3.3 |
| jupyter/extension-templategeneric | >=0 <4.3.3 | 4.3.3 |
| jupyterlabpypi | >=0 <4.3.0 | 4.3.0 |
Published upstream
Jul 16, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 3, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 8, 2026
JupyterLab extension template is a `copier` template for JupyterLab extensions. Repositories created using this template with `test` option include `update-integration-tests.yml` workflow which has an RCE vulnerability. Extension authors hosting their code on GitHub are urged to upgrade the template to the latest version. Users who made changes to `update-integration-tests.yml`, accept overwriting of this file and re-apply your changes later. Users may wish to temporarily disable GitHub Actions while working on the upgrade. We recommend rebasing all open pull requests from untrusted users as actions may run using the version from the `main` branch at the time when the pull request was created. Users who are upgrading from template version prior to 4.3.0 may wish to leave out proposed changes to the release workflow for now as it requires additional configuration.
Quoted source text, attributed separately from HOL analysis.