CVE-2026-12261: Improper Access Control in nltk/nltk
A vulnerability in nltk.downloader in nltk/nltk versions <= 3.9.4 allows for cross-package resource and model poisoning. The downloader extracts package archives into shared namespaces such as corpora/ and taggers/ instead of package-isolated roots, and validates package integrity only after the archive has been written and extracted. This design flaw enables one package to overwrite another package's trusted resources within the same namespace, making the changes immediately active through ordinary NLTK APIs. This issue persists across fresh interpreter restarts and can affect downstream workflows, including machine learning pipelines and reproducibility-sensitive environments.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-12261?
CVE-2026-12261 has a medium severity rating of 5.3.
How do I fix CVE-2026-12261?
To fix CVE-2026-12261, upgrade nltk/nltk to version 3.9.5 or later, which addresses the improper access control.
What types of attacks are possible with CVE-2026-12261?
CVE-2026-12261 allows for cross-package resource and model poisoning due to improper access control in the nltk.downloader.
Which versions of nltk/nltk are affected by CVE-2026-12261?
CVE-2026-12261 affects nltk/nltk versions 3.9.4 and earlier.
What are the implications of exploiting CVE-2026-12261?
Exploiting CVE-2026-12261 could lead to the corruption of shared resources in nltk/nltk, impacting model integrity.