CVE-2024-39705

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.3% (71st percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 7.5 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2024-06-28) is not newer than that change (2026-04-15), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2024-0118 (ENISA EUVD) · GHSA-cgvx-9447-vcch (GitHub Security Advisories) · PYSEC-2024-167 (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).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.3%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

NLTK through 3.8.1 allows remote code execution if untrusted packages have pickled Python code, and the integrated data package download functionality is used. This affects, for example, averaged_perceptron_tagger and punkt.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
60
EG Risk 60/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.
Exploitation1.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (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.3%
EPSS %ILE
71st
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.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). 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 or medium mission impact; Attend at high (mission-essential systems).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 or medium mission impact; Attend at high (mission-essential systems).

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

Exploitation none (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

June 27, 2024

Last Modified

April 15, 2026

Advisory Details (3)

Auto-updated Oct 8, 2026
Patch available.
Web page

RCE in Python NLTK (CVE-2024-39705) - vsociety

https://www.vicarius.io/vsociety/posts/rce-in-python-nltk-cve-2024-39705-39706
Web page

Remote code execution vulnerability in NLTK · Issue #3266 · nltk/nltk · GitHub

https://github.com/nltk/nltk/issues/3266
Web page

Security issues with pickles · Issue #2522 · nltk/nltk · GitHub

https://github.com/nltk/nltk/issues/2522

Vendor Advisories for CVE-2024-39705(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipnltk @ 3.9 (fixes < 3.9)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
nltk3.10.0-1 ... 3.9.3-1 (12 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
nltk3.10.0-1 ... 3.9.3-1 (9 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
nltk—
  • every version up to 3.9.1-1: fixed in 3.9.1-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
nltk—
  • every version up to 3.9.1-1: fixed in 3.9.1-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
nltk0.8 ... 3.9b1 (60 versions)
  • every version up to 3.9: fixed in 3.9
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 43× 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 281 rows on record for this CVE, as 99 entries (1 repeat 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 181 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2024-39705?
CVE-2024-39705 is a critical-severity vulnerability; its CVE record was published on June 27, 2024. NLTK through 3.8.1 allows remote code execution if untrusted packages have pickled Python code, and the integrated data package download functionality is used. This affects, for example, averaged_perceptron_tagger and punkt.
When was the CVE record for CVE-2024-39705 published?
The CVE record for CVE-2024-39705 was published on June 27, 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 April 15, 2026; the record at its source may have been updated since.
Is CVE-2024-39705 actively exploited?
CVE-2024-39705 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.3% probability of exploitation in the next 30 days (71st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-39705?
CVE-2024-39705 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2024-39705?
A fix for CVE-2024-39705 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-39705 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2024-39705?

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

Book a Demo →Browse All CVEs