[GHSA-68j8-pq59-fqgm] NLTK has a Path Traversal issue - #9198
Open
antonisloukis wants to merge 1 commit into
Open
[GHSA-68j8-pq59-fqgm] NLTK has a Path Traversal issue#9198antonisloukis wants to merge 1 commit into
antonisloukis wants to merge 1 commit into
Conversation
github-actions
Bot
changed the base branch from
main
to
antonisloukis/advisory-improvement-9198
August 24, 2026 19:55
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates
Comments
NLTK 3.9.3 contains the upstream fix for this path traversal vulnerability, but the advisory currently lists no patched version.
Upstream PR #3479, "Prevent path traversal & absolute-path access in CorpusReader.open() (CWE-22)", was merged as commit 603e34d25a2cad4612185ebfa6bc1c0dcfcfb2ab.
The official NLTK 3.9.3 ChangeLog explicitly lists:
"Block path traversal/abs paths in corpus readers and FS pointers (#3479, #3480)"
Therefore, the patched version should be recorded as 3.9.3. I have also added the upstream PR, fix commit, and 3.9.3 ChangeLog as supporting references.