NLTK denial of service via recursion in DependencyGraph.tree()
Affects NLTK when a crafted CoNLL or Malt-TAB dependency file with a long chain of linked tokens is loaded and .tree() or .triples() is then called on the graph. Fixed in 3.10.4.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.10.4
- Who is exposed
- Default setups
Summary
Natural Language Toolkit (NLTK), a Python library for natural language processing, has an uncontrolled recursion flaw in its dependency graph tree and triples functions. A crafted CoNLL or Malt-TAB dependency file with a long enough chain can crash the process that calls these functions, and an attacker can trigger this remotely without logging in.
Written by a model
Original description
NLTK (Natural Language Toolkit) is a suite of open source Python modules, data sets, and tutorials supporting research and development in Natural Language Processing. Prior to 3.10.4, DependencyGraph.tree and DependencyGraph.triples walk parsed dependency edges through unbounded Python recursion and do not use a working cycle or depth guard. A crafted CoNLL or Malt-TAB dependency file containing a sufficiently long chain can raise RecursionError when the documented traversal APIs are called, aborting the current worker. This issue is fixed in version 3.10.4.
What to do
Check every install: default setups are affected.
Upgrade to a fixed version: 3.10.4.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129222 (Natural Language Toolkit (NLTK): Uncontrolled recursion (crash DoS) in DependencyGraph.tree()/triples()), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129222 (entry last updated 2026-11-19):
Affected:
- nltk nltk: fixed in 3.10.4
Fixed versions: 3.10.4.
Conditions (all must be true for the bug to be hit):
- A crafted CoNLL or Malt-TAB dependency file with a long chain of linked tokens is loaded (source: https://github.com/nltk/nltk/security/advisories/GHSA-rh8m-wqhc-qmrf)
- The application then calls .tree() or .triples() on the parsed graph (source: https://github.com/nltk/nltk/security/advisories/GHSA-rh8m-wqhc-qmrf)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-129222 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129222 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/nltk/nltk/security/advisories/GHSA-rh8m-wqhc-qmrf
- https://github.com/nltk/nltk/pull/3885
- https://github.com/nltk/nltk/commit/a74682757cee8c11128ad277d2f2bd0b8e1884ff
- https://github.com/nltk/nltk/releases/tag/v3.10.4
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129222
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129222"}.Affected versions
- nltk nltkfixed in 3.10.4
cve.now Index
- Exploitation0/40No signal
- Exposure25/25Default setups, CISA rates it automatable
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 73 if added to CISA KEV
- Would score about 68 if CISA's SSVC rates exploitation active
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · nltk/nltk · Advisory GHSA-rh8m-wqhc-qmrf |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129222 |
| Record | NVD · CVE-2026-129222 |
| Other links 3 | |
| Repository | GitHub · nltk/nltk · Pull request #3885 |
| Repository | GitHub · nltk/nltk · Commit a7468275 |
| Repository | GitHub · nltk/nltk · Release v3.10.4 |
Questions about CVE-2026-129222
Is CVE-2026-129222 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
Calling .tree() or .triples() on a parsed dependency graph recurses too deeply when the graph is a long chain of linked tokens. This raises an unhandled RecursionError that crashes the process or worker.
Source: github.com
Which versions are affected by CVE-2026-129222?
nltk: before 3.10.4.
Source: cve.now feed data
Am I affected, and how do I check?
The affected package is nltk, in versions before 3.10.4. The setup is loading a CoNLL or Malt-TAB dependency file and then calling .tree() or .triples() on the resulting graph. To check an installed version, run 'pip show nltk' or 'python -c "import nltk; print(nltk.__version__)"'.
Source: github.com
How do I fix CVE-2026-129222?
Upgrade nltk to 3.10.4 or later, which is the fixed version listed for this vulnerability.
Source: github.com
Related
- CVE-2026-128138NLTK incomplete fix: additional JVM/JAR sandbox bypass through unvalidated launcher tokens in java() command arguments
- CVE-2026-128134NLTK dot2img runs Graphviz 'dot' without the trusted-exec chokepoint, enabling local code execution via a writable PATH element
- CVE-2026-129223Natural Language Toolkit (NLTK): Uncontrolled recursion (crash DoS) in Synset.tree()/acyclic_tree() via WordNet relation traversal
- CVE-2026-128139NLTK: XMLCorpusView comment and CDATA parsing permits quadratic CPU denial of service
- CVE-2026-129229NLTK: Compile-time regex DoS in NLTK search/tokenizer sinks: quadratic regex-engine compile bypasses the match-only timeout
- CVE-2026-129234NLTK: Untrusted search path in prover9/mace4 config allows local code execution via relative binary_location
No corrections so far. Something wrong on this page? Report an error.