Kurz gesagt
- CVE-2026-0848 ist eine Schwachstelle (KRITISCH (CVSS 10.0)) in nltk, nltk (nltk).
- Wahrscheinlichkeit einer Ausnutzung in den nächsten 30 Tagen (EPSS): 0.84%, höher als bei 57.9% aller Schwachstellen.
- Abhilfe: auf 3.9.3 oder neuer aktualisieren.
| Package | Affected versions | Patched versions |
|---|
| nltk PyPI | < 3.9.3
| 3.9.3
|
| nltk | ≤ 3.9.2
| No fix yet |
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.
NVD 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.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free