What is CVE-2026-0848?
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.
Timeline
- 2026-03-05Published to the U.S. National Vulnerability Database (NVD)
- 2026-06-17NVD record last updated
Affected product
Nltk
Remediation Steps
- Review OpenCode Systems gateway access controls and multi-tenancy implementation
- Apply security patch restricting authenticated user access to authorized tenant scopes only
- Audit recent logs for unauthorized cross-tenant SMS message access
- Implement role-based access control (RBAC) enforcement in gateway
- Test tenant isolation measures in staging environment
References
Referenced in our briefings & reports
- Vulnerability Priority Report – Week 5 of March 2026 (March 30 – April 5)
Browse all tracked CVEs in the defend.network CVE database →
🤖 This CVE page is generated by defend.network from NVD, CISA KEV, EPSS, and our verified daily briefings. Severity and exploitation data come from official sources; always verify remediation steps against the official vendor advisory before acting in production.