Skip to content
Applications

CVE-2025-14009

10.0
Critical
EPSS 0.79%Patch availableFeb 19, 2026

Critical remote code execution in NLTK downloader via unvalidated zip extraction.

common questions

Is CVE-2025-14009 being exploited?

Not confirmed. CVE-2025-14009 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.79% probability of exploitation in the next 30 days.

How severe is CVE-2025-14009?

CVE-2025-14009 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-14009?

Yes. A fix has been recorded for CVE-2025-14009. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2025-14009 affect?

CVE-2025-14009 affects NLTK downloader (nltk.downloader) in Python environments, Python apps relying on NLTK data download. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2025-14009?

Upgrade to patched NLTK version when available; validate sources.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
NLTK downloader (nltk.downloader) in Python environmentsPython apps relying on NLTK data download
impact

Remote code execution via crafted zip during NLTK downloader extraction; attacker could run arbitrary code in the Python process.

action required

Patch when possible

affected versions
nltk nltk/nltk
  • affected<= latest

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free