CVE-2026-0846
Arbitrary File Read in NLTK 3.9.2 filestring() Function
Publication date: 2026-03-09
Last updated on: 2026-04-17
Assigner: huntr.dev
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| nltk | nltk | 3.9.2 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-36 | The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize absolute path sequences such as "/abs/path" that can resolve to a location that is outside of that directory. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the filestring() function of the nltk.util module in nltk version 3.9.2. The function improperly validates input paths and directly opens files specified by user input without sanitization. This allows attackers to read arbitrary files on the system by providing absolute or traversal paths.
How can this vulnerability impact me? :
The vulnerability can be exploited both locally and remotely, especially in environments where the filestring() function is used in web APIs or other interfaces that accept user input. Exploitation can lead to unauthorized access to sensitive system files, potentially exposing confidential information and causing confidentiality, integrity, and availability impacts.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know