Vulnerability Description
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 Score
CRITICAL
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Nltk | Nltk | <= 3.9.2 |
Related Weaknesses (CWE)
References
- https://huntr.com/bounties/08b109bb-ac24-403f-9422-1c246ce60202ExploitVendor Advisory
- https://huntr.com/bounties/08b109bb-ac24-403f-9422-1c246ce60202ExploitVendor Advisory
FAQ
What is CVE-2026-0848?
CVE-2026-0848 is a vulnerability with a CVSS score of 10.0 (CRITICAL). 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 verific...
How severe is CVE-2026-0848?
CVE-2026-0848 has been rated CRITICAL with a CVSS base score of 10.0/10. This is considered a critical vulnerability requiring immediate attention.
Is there a patch for CVE-2026-0848?
Check the references section above for vendor advisories and patch information. Affected products include: Nltk Nltk.