NLTK 在 3.10.3 版本之前存在一个服务器端请求伪造(SSRF)漏洞,该漏洞位于 函数中(以及调用该函数的 、 等方法),前提是系统中配置了 HTTP 代理。虽然 会在本地对请求的主机名进行验证,但由于代理处理程序的继承机制禁用了安全的 HTTP/HTTPS 处理器,实际的数据获取请求由代理转发,而目标地址在代理层面不再进行任何验证。攻击者可以提供一个经本地验证的公共 URL,该 URL 被代理转发至仅允许内部回环地址访问的服务,从而导致内部 HTTP 资源的泄露、伪造的下载器索引文件的加载,以及攻击者自定
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
| # | POC Description | Source Link | Shenlong Link |
|---|
| CVE-2026-79657 | 9.8 CRITICAL | NLTK before 3.10.3 Remote Code Execution via Unsafe Pickle Deserialization |
| CVE-2026-79675 | 9.8 CRITICAL | NLTK before 3.10.3 JVM Argument Injection via Per-Call Options |
| CVE-2026-78683 | 9.6 CRITICAL | NLTK before 3.10.0 Remote Code Execution via Unsafe Pickle Deserialization |
| CVE-2026-79674 | 8.2 HIGH | NLTK 3.10.2 Path Traversal via corpus-reader constructors |
| CVE-2026-78680 | 7.8 HIGH | NLTK before 3.10.3 Arbitrary Code Execution via Graphviz dot Binary |
| CVE-2026-78681 | 7.5 HIGH | NLTK before 3.10.3 Entity Expansion DoS via ElementTree |
| CVE-2026-79676 | 5.9 MEDIUM | NLTK before 3.10.3 Path Traversal via Symlink Bypass |
No comments yet