cve.bz

CVE-2026-128140 NLTK: Downloader cyclic collection indices cause an infinite closure walk

6.5 mediumEPSS 0.4%Fix available

Medium (6.5) in nltk nltk. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in nltk 3.10.4.

On this page
NLTK (Natural Language Toolkit) is a suite of open source Python modules, data sets, and tutorials supporting research and development in Natural Language Processing. From 3.6.7 until 3.10.4, nltk.downloader follows collection membership without tracking already visited collection nodes. A self-referencing or mutually referencing collection index can therefore make the package-closure walk loop indefinitely while its queue and memory usage grow, denying service when a victim processes the attacker-influenced index. This issue is fixed in version 3.10.4.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
EPSS
0.4% estimated probability of exploitation activity in the next 30 days; 30th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-11-19. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-835 Loop with Unreachable Exit Condition (Infinite Loop)
Published
Modified
Assigned by
GitHub_M (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • nltk (PyPI): fixed in 3.10.4

Ask an AI about this CVE

Show the promptExplain CVE-2026-128140 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-128140?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-128140?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-128140 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
nltk>= 3.6.7, < 3.10.4

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-pcm8-fqjx-rvx8PyPInltk>=3.6.7 <3.10.43.10.4

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14nltkno fix listedDEBIAN-CVE-2026-128140

From the distributions' data via OSV.dev: the Debian Security Tracker. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian.

References

Check your stackJSON