No data.
No data.
OpenCVE Enrichment is a feature of OpenCVE that uses AI to automatically link vendors and products to CVEs. Learn more on GitHub.
| Vendors | Products |
|---|---|
|
Nltk
Subscribe
|
Nltk/nltk
Subscribe
|
| Source | ID | Title |
|---|---|---|
 Github GHSA |
GHSA-m42h-3232-vpv3 | nltk: Arbitrary File Read via Path Traversal in nltk.data.load() through Percent-Encoded Sequences |
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Tue, 18 Aug 2026 09:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Path Traversal via Percent-Encoding in nltk.data.find() and nltk.data.load() | nltk: NLTK: Information disclosure via path traversal vulnerability |
| CPEs | ||
| Vendors & Products |
Nltk nltk
|
|
| Metrics |
cvssV3_0
|
Tue, 18 Aug 2026 09:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | NLTK version 3.9.4 is vulnerable to a path traversal attack due to an incomplete fix for GitHub Issue #3504. The `_UNSAFE_NO_PROTOCOL_RE` regex in `nltk/data.py` checks for literal `../` sequences but fails to account for percent-encoded traversal sequences such as `..%2f`. The `url2pathname()` function decodes these sequences after the validation step, allowing an attacker to bypass the protection. This vulnerability enables an attacker to read arbitrary files accessible to the Python process by controlling the resource name parameter passed to `nltk.data.load()` or `nltk.data.find()`. The issue affects applications that rely on NLTK for resource loading, including NLP web applications, Jupyter notebooks, and CLI tools. The default `pathsec.ENFORCE=False` setting exacerbates the impact by not blocking the file read at the `open()` stage. | This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
Wed, 01 Jul 2026 00:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
Tue, 30 Jun 2026 14:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 30 Jun 2026 05:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Nltk
Nltk nltk/nltk |
|
| Vendors & Products |
Nltk
Nltk nltk/nltk |
Tue, 30 Jun 2026 01:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | NLTK version 3.9.4 is vulnerable to a path traversal attack due to an incomplete fix for GitHub Issue #3504. The `_UNSAFE_NO_PROTOCOL_RE` regex in `nltk/data.py` checks for literal `../` sequences but fails to account for percent-encoded traversal sequences such as `..%2f`. The `url2pathname()` function decodes these sequences after the validation step, allowing an attacker to bypass the protection. This vulnerability enables an attacker to read arbitrary files accessible to the Python process by controlling the resource name parameter passed to `nltk.data.load()` or `nltk.data.find()`. The issue affects applications that rely on NLTK for resource loading, including NLP web applications, Jupyter notebooks, and CLI tools. The default `pathsec.ENFORCE=False` setting exacerbates the impact by not blocking the file read at the `open()` stage. | |
| Title | Path Traversal via Percent-Encoding in nltk.data.find() and nltk.data.load() | |
| Weaknesses | CWE-22 | |
| References |
| |
| Metrics |
cvssV3_0
|
Projects
Sign in to view the affected projects.
MITRE
Status: REJECTED
Assigner: @huntr_ai
Published:
Updated: 2026-08-18T08:33:26.727Z
Reserved: 2026-06-15T06:24:30.096Z
Link: CVE-2026-12243
Vulnrichment
Updated:
NVD
Status : Rejected
Published: 2026-06-30T01:16:29.063
Modified: 2026-08-18T09:16:47.450
Link: CVE-2026-12243
Redhat
OpenCVE Enrichment
Updated: 2026-06-30T05:00:03Z