CVE-2026-0848: critical vulnerability in nltk/nltk
Arbitrary Code Execution in NLTK StanfordSegmenter via Untrusted JAR Loading
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
28Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 10epss 0.8%
NLTK versions <=3.9.2 are vulnerable to arbitrary code execution due to improper input validation in the StanfordSegmenter module. The module dynamically loads external Java .jar files without verification or sandboxing. An attacker can supply or replace the JAR file, enabling the execution of arbitrary Java bytecode at import time. This vulnerability can be exploited through methods such as model poisoning, MITM attacks, or dependency poisoning, leading to remote code execution. The issue arises from the direct execution of the JAR file via subprocess with unvalidated classpath input, allowing malicious classes to execute when loaded by the JVM.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Affected products
nltk · nltk/nltkRelated CVEs — nltk/nltk
In the same product, most dangerous first.
CVE-2021-3828HIGHInefficient Regular Expression Complexity in nltk/nltkEPSS 1.6%CVE-2021-3842HIGHInefficient Regular Expression Complexity in nltk/nltkEPSS 1.6%CVE-2025-14009HIGHZip Slip Vulnerability in nltk/nltk Leading to Remote Code ExecutionEPSS 1.0%CVE-2026-0847HIGHPath Traversal in nltk/nltkEPSS 1.0%CVE-2026-0846HIGHArbitrary File Read via Absolute Path Input in nltk.util.filestring()EPSS 0.6%CVE-2026-12199HIGHUnauthenticated Denial of Service in nltk.app.wordnet_appEPSS 0.3%