CVE-2024-39700

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 1.1% (65th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated

Also known asEUVD-2024-38192 (ENISA EUVD) · PYSEC-2024-322 (OSV.dev)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 1.1%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.1%
EPSS %ILE
65th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
1.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 16, 2024

Last Modified

November 4, 2026

Advisory Details (2)

Auto-updated Nov 7, 2026
Patch available. Sources: github, github_commit.
GitHub commit Patch Available

commit 035e78c1c65b (jupyterlab/extension-template)

Patch available: jupyterlab/extension-template v4.3.3 (contains commit 035e78c1c65b)

https://github.com/jupyterlab/extension-template/commit/035e78c1c65bcedee97c95bb683abe59c96bc4e6
GitHub advisoryMentions a patch (unverified)

Remote Code Execution vulnerability in `update-integration-tests` GitHub Action workflow · Advisory · jupyterlab/extension-template · GitHub

https://github.com/jupyterlab/extension-template/security/advisories/GHSA-45gq-v5wm-82wg

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
jupyterlab0.0.1 ... 4.3.0rc1 (539 versions)
  • every version up to 4.3.0: fixed in 4.3.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 32× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 253 rows on record for this CVE, as 98 entries (2 repeats merged).

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 153 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:47 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  2. 2026-11-13 05:57 UTCEchelonGraph re-scored
  3. 2026-11-12 16:31 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  4. 2026-11-12 05:19 UTCEchelonGraph re-scored
  5. 2026-11-11 16:35 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  6. 2026-11-11 04:41 UTCEchelonGraph re-scored
  7. 2026-11-10 16:38 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  8. 2026-11-10 04:02 UTCEchelonGraph re-scored
  9. 2026-11-09 16:31 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  10. 2026-11-09 03:24 UTCEchelonGraph re-scored
  11. 2026-11-08 16:36 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  12. 2026-11-08 02:46 UTCEchelonGraph re-scored
  13. 2026-11-07 16:36 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  14. 2026-11-07 02:08 UTCEchelonGraph re-scored
  15. 2026-11-06 16:32 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  16. 2026-11-06 01:28 UTCEchelonGraph re-scored
  17. 2026-11-05 16:34 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  18. 2026-11-05 01:55 UTCOSV refresh
  19. 2026-11-05 00:50 UTCEchelonGraph re-scored
  20. 2026-11-04 16:32 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  21. 2026-11-03 22:27 UTCEchelonGraph re-scored▼ 0.10
  22. 2026-11-03 22:26 UTCNVD updateCVSS v3 → 9.8
  23. 2026-11-03 21:56 UTCEchelonGraph re-scored
  24. 2026-11-03 16:42 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  25. 2026-11-03 14:32 UTCEchelonGraph re-scored
Show 73 more
  1. 2026-11-02 16:41 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  2. 2026-11-02 13:37 UTCEchelonGraph re-scored
  3. 2026-11-01 16:31 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  4. 2026-11-01 12:58 UTCEchelonGraph re-scored
  5. 2026-10-31 16:30 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  6. 2026-10-31 12:21 UTCEchelonGraph re-scored
  7. 2026-10-30 16:32 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  8. 2026-10-30 11:42 UTCEchelonGraph re-scored
  9. 2026-10-29 16:30 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  10. 2026-10-29 11:05 UTCEchelonGraph re-scored
  11. 2026-10-28 16:29 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  12. 2026-10-28 10:18 UTCEchelonGraph re-scored
  13. 2026-10-27 16:29 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  14. 2026-10-27 08:43 UTCEchelonGraph re-scored
  15. 2026-10-26 16:29 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  16. 2026-10-25 17:06 UTCEchelonGraph re-scored
  17. 2026-10-25 16:30 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  18. 2026-10-25 05:30 UTCEchelonGraph re-scored
  19. 2026-10-24 16:30 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  20. 2026-10-24 04:52 UTCEchelonGraph re-scored
  21. 2026-10-23 16:29 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  22. 2026-10-23 04:13 UTCEchelonGraph re-scored
  23. 2026-10-22 16:31 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  24. 2026-10-22 03:33 UTCEchelonGraph re-scored
  25. 2026-10-21 16:29 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  26. 2026-10-21 02:54 UTCEchelonGraph re-scored
  27. 2026-10-20 16:30 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  28. 2026-10-20 02:14 UTCEchelonGraph re-scored
  29. 2026-10-19 16:29 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  30. 2026-10-19 01:32 UTCEchelonGraph re-scored
  31. 2026-10-18 16:30 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  32. 2026-10-18 07:09 UTCEchelonGraph re-scored
  33. 2026-10-18 00:53 UTCEchelonGraph re-scored
  34. 2026-10-17 16:31 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  35. 2026-10-17 00:13 UTCEchelonGraph re-scored
  36. 2026-10-16 16:36 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  37. 2026-10-15 21:18 UTCEchelonGraph re-scored
  38. 2026-10-15 16:30 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  39. 2026-10-14 16:30 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  40. 2026-10-14 15:20 UTCEchelonGraph re-scored
  41. 2026-10-13 16:30 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  42. 2026-10-12 17:49 UTCEchelonGraph re-scored
  43. 2026-10-12 16:31 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  44. 2026-10-11 21:14 UTCEchelonGraph re-scored
  45. 2026-10-11 16:07 UTCEchelonGraph re-scored
  46. 2026-10-11 13:46 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  47. 2026-10-10 19:58 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  48. 2026-10-10 14:03 UTCOSV refresh
  49. 2026-10-09 20:05 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  50. 2026-10-08 17:07 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  51. 2026-10-07 23:46 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  52. 2026-10-06 15:15 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  53. 2026-10-05 17:41 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  54. 2026-10-03 14:24 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  55. 2026-10-01 19:48 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  56. 2026-09-30 19:49 UTCEchelonGraph re-scored
  57. 2026-09-30 15:01 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  58. 2026-09-29 15:17 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  59. 2026-09-28 13:49 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  60. 2026-09-27 13:44 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  61. 2026-09-26 15:57 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  62. 2026-09-26 00:23 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  63. 2026-09-24 14:01 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  64. 2026-09-23 13:46 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  65. 2026-09-22 14:46 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  66. 2026-09-21 20:32 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  67. 2026-09-20 23:36 UTCOSV refresh
  68. 2026-09-19 15:40 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  69. 2026-09-18 19:26 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  70. 2026-09-16 14:06 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  71. 2026-09-15 03:08 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  72. 2026-09-13 16:45 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  73. 2026-09-12 14:59 UTCEPSS rescoreEPSS 1.0% · 61st percentile

Frequently asked(5)

What is CVE-2024-39700?
CVE-2024-39700 is a critical-severity vulnerability; its CVE record was published on July 16, 2024. 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…
When was the CVE record for CVE-2024-39700 published?
The CVE record for CVE-2024-39700 was published on July 16, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 4, 2026; the record at its source may have been updated since.
Is CVE-2024-39700 actively exploited?
CVE-2024-39700 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% probability of exploitation in the next 30 days (65th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-39700?
CVE-2024-39700 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2024-39700?
A fix for CVE-2024-39700 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-39700

Explore →

Is Your Infrastructure Affected by CVE-2024-39700?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.