CVE-2024-39705

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.

Published: 2024-06-27 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-39705 is rated Moderate Risk (57.9/100): CVSS Critical severity, with medium exploitation likelihood (EPSS 1.35%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-39705

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 10.79% 1.35% -9.45%
2 2026-04-23 11.05% 10.79% -0.26%
3 2026-04-21 — 11.05% —

Full EPSS history (16 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-39705

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2024-39705

GitHub Security Advisory for CVE-2024-39705

GHSA-cgvx-9447-vcch · Severity: high · Ecosystem: pip — ntlk unsafe deserialization vulnerability

OS Trackers for CVE-2024-39705

vendor priority summary link
debian not yet assigned CVE-2024-39705 not yet assigned priority: Debian including 1 source packages (nltk), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 3, open 2. https://security-tracker.debian.org/tracker/CVE-2024-39705
ubuntu medium CVE-2024-39705 medium priority: Ubuntu including 1 source packages (nltk), 9 status rows across 9 suites (bionic, focal, jammy, mantic, noble, oracular, trusty, upstream, xenial): ignored 8, released 1. https://ubuntu.com/security/CVE-2024-39705

Affected software / configurations for CVE-2024-39705

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2024-39705

cvelogic Threat Intelligence