CVE-2026-0848 Affecting nltk package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-ECHOLATEST-NLTK-18321526
- published27 Jul 2026
- disclosed5 Mar 2026
Introduced: 5 Mar 2026
CVE-2026-0848 (opens in a new tab)How to fix?
There is no fixed version for Echo:latest nltk.
NVD Description
Note: Versions mentioned in the description apply only to the upstream nltk package and not the nltk package as distributed by Echo.
See How to fix? for Echo:latest relevant fixed versions and status.
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.