NLTK · GHSA-f7j6-hf97-9v99 · Package
NO FIX YET · SEE WHAT TO DO
This advisory is withdrawn as a duplicate of GHSA-fg9w-wfp5-j933. The original text says NLTK 3.10.0 before 3.10.4 lets an attacker supply unvalidated model paths to BllipParser, so the C extension opens files outside the NLTK data roots and can block on FIFOs and devices.
first public Nov 13, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Applications that pass untrusted input into BllipParser model paths in NLTK 3.10.0 through 3.10.4. Systems that only use fixed, trusted model paths are less exposed. The advisory itself is withdrawn, so the original fix record is GHSA-fg9w-wfp5-j933.
Not affected if fixed-model-paths, no-bllipparser-use
Who cares nlp, nltk, python
pip show nltk.parser_model, reranker_features, reranker_weights, or from_unified_model_dir() in BllipParser.nltk 3.10.4 (fixed version in the product data; the withdrawn advisory points to GHSA-fg9w-wfp5-j933 for the fix)This advisory has been withdrawn because it is a duplicate of GHSA-fg9w-wfp5-j933. This link is maintained to preserve external references.
NLTK from 3.10.0 before 3.10.4 contains an arbitrary file read vulnerability in BllipParser that allows attackers to open files outside NLTK data roots by supplying unvalidated model paths. Attackers controlling parser_model, reranker_features, reranker_weights, or from_unified_model_dir() input can make the bllipparser C extension read sensitive files or block on FIFOs and devices.
This page as .md · .json · CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L
GitHub Advisory Database, CC-BY 4.0. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.