NLTK denial of service via recursion in WordNet tree traversal
Only affects NLTK applications that load a custom or foreign WordNet-format resource and call Synset.tree() or Synset.acyclic_tree() with the default unbounded depth. Fixed in NLTK 3.10.4.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.10.4
- Who is exposed
- Specific setups only
Summary
Natural Language Toolkit (NLTK) is affected. An attacker who can influence a custom or foreign WordNet-format resource that an application loads can make deep recursion in `Synset.tree()` and `acyclic_tree()` crash the traversal or worker, causing a denial of service. The attack can be launched remotely, without logging in and without any user action.
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, WordNet Synset.tree and acyclic_tree traverse relation graphs through recursive utility helpers without a depth bound. Exploitation requires the host application to load an attacker-influenced custom or foreign WordNet-format lexical resource; no relation in NLTK's bundled WordNet 3.0 corpus reaches the crash threshold. An excessively deep relation graph in such a resource can exceed the Python recursion limit and terminate the traversal or request worker. This issue is fixed in version 3.10.4.
Who should check
Teams running NLTK 3.10.3 or earlier that load custom or foreign WordNet-format lexical resources and call Synset.tree() or Synset.acyclic_tree()
“requires the host application to load a custom/foreign WordNet-format lexical resource”
What to do
Check whether your setup matches what the bug needs.
The host application loads a custom or foreign WordNet-format lexical resource rather than NLTK's bundled default corpus. The application calls Synset.tree() or Synset.acyclic_tree() with the default unbounded depth; .closure() is not 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-129223 (Natural Language Toolkit (NLTK): Uncontrolled recursion (crash DoS) in Synset.tree()/acyclic_tree() via WordNet relation traversal), 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-129223 (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):
- The host application loads a custom or foreign WordNet-format lexical resource rather than NLTK's bundled default corpus. (source: https://github.com/nltk/nltk/security/advisories/GHSA-8846-p9w9-5frf)
- The application calls Synset.tree() or Synset.acyclic_tree() with the default unbounded depth; .closure() is not affected. (source: https://github.com/nltk/nltk/security/advisories/GHSA-8846-p9w9-5frf)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-129223 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129223 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-8846-p9w9-5frf
- https://github.com/nltk/nltk/commit/0e474a7d73c95b42aa2c792f364e4f9bf4096c56
- 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-129223
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-129223"}.Affected versions
- nltk nltkfixed in 3.10.4
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- 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 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
Timeline
- CVE published
- First seen by cve.now
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · nltk/nltk · Advisory GHSA-8846-p9w9-5frf |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129223 |
| Record | NVD · CVE-2026-129223 |
| Other links 2 | |
| Repository | GitHub · nltk/nltk · Commit 0e474a7d |
| Repository | GitHub · nltk/nltk · Release v3.10.4 |
Questions about CVE-2026-129223
Is CVE-2026-129223 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?
A long chain of WordNet relations that does not loop back on itself can make the tree traversal recurse too deeply. Python then raises an unhandled RecursionError, which can crash the traversal or the worker process.
Source: github.com
Which versions are affected by CVE-2026-129223?
nltk: before 3.10.4.
Source: cve.now feed data
Am I affected, and how do I check?
Affected setups are NLTK versions before 3.10.4 where the application loads a custom or foreign WordNet-format lexical resource instead of NLTK's bundled default corpus, and calls Synset.tree() or Synset.acyclic_tree() without a depth limit. Check the installed version with pip show nltk, and search the code for calls to .tree( or .acyclic_tree( on synsets. Synset.closure() is not affected.
Source: github.com
How do I fix CVE-2026-129223?
Upgrade NLTK to 3.10.4 or later.
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-128139NLTK: XMLCorpusView comment and CDATA parsing permits quadratic CPU denial of service
- CVE-2026-129222Natural Language Toolkit (NLTK): Uncontrolled recursion (crash DoS) in DependencyGraph.tree()/triples()
- 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.