nltk: A vulnerability in NLTK versions up to and including 3.9.2 allows arbitrary file read via path traversal in multiple...
CVE-2026-0847 is fixed in 3 products on 1 platform, first by DEBIAN-CVE-2026-0847, released March 4, 2026. It is not reported as exploited. Patch Radar priority: High.
A vulnerability in NLTK versions up to and including 3.9.2 allows arbitrary file read via path traversal in multiple CorpusReader classes, including WordListCorpusReader, TaggedCorpusReader, and BracketParseCorpusReader. These classes fail to properly sanitize or validate file paths, enabling attackers to traverse directories and access sensitive files on the server. This issue is particularly critical in scenarios where user-controlled file inputs are processed, such as in machine learning APIs, chatbots, or NLP pipelines. Exploitation of this vulnerability can lead to unauthorized access to sensitive files, including system files, SSH private keys, and API tokens, and may potentially escalate to remote code execution when combined with other vulnerabilities.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| nltk · Debian 14 | 3.9.3-1 | DEBIAN-CVE-2026-0847 | Mar 4, 2026 |
| python-nltk · Ubuntu 18.04.6 LTS (bionic) | 3.2.5-1ubuntu0.1+esm4 | python-nltk 3.2.5-1ubuntu0.1+esm4 | Mar 20, 2026 |
| python3-nltk · Ubuntu 18.04.6 LTS (bionic) | 3.2.5-1ubuntu0.1+esm4 | python3-nltk 3.2.5-1ubuntu0.1+esm4 | Mar 20, 2026 |
| python3-nltk · Ubuntu 20.04 LTS (focal) | 3.4.5-2ubuntu0.1~esm4 | python3-nltk 3.4.5-2ubuntu0.1~esm4 | Mar 20, 2026 |
| python3-nltk · Ubuntu 22.04.1 LTS (jammy) | 3.7-1ubuntu0.1~esm2 | python3-nltk 3.7-1ubuntu0.1~esm2 | Mar 20, 2026 |
| python3-nltk · Ubuntu 24.04.5 LTS (noble) | 3.8.1-1ubuntu0.1~esm2 | python3-nltk 3.8.1-1ubuntu0.1~esm2 | Mar 20, 2026 |
| python3-nltk · Ubuntu 26.04.1 LTS (resolute) | 3.9.2-1ubuntu0.1~esm2 | python3-nltk 3.9.2-1ubuntu0.1~esm2 | Mar 20, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.