NLTK denial of service via regex compile in tokenizer
Only affects NLTK 3.10.0 through 3.10.3 when caller-supplied text is used as the regex search pattern in TokenSearcher.findall() / Text.findall() or as the RegexpTokenizer pattern. Fixed in 3.10.4.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.10.4
- Who is exposed
- Not reported
Summary
NLTK, the Natural Language Toolkit for Python, contains a flaw in its search and tokenizer functions that lets an attacker remotely, without logging in, send a regular expression that takes a very long time to compile and uses up CPU, denying service. The problem is in the work done before the match timeout starts, so the timeout does not stop it.
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. From 3.10.0 until 3.10.4, TokenSearcher.findall and Text.findall accept caller-controlled regular expressions with an unbounded number of capturing groups throughout the affected range. Starting in 3.10.3, nltk.redos.compile and RegexpTokenizer expose the same compile-time vector. The third-party regex engine compiles group-dense patterns with roughly quadratic cost before the match-time timeout begins, allowing a small unauthenticated request to exhaust CPU and deny service. This issue is fixed in version 3.10.4.
Who should check
Teams running NLTK 3.10.0 through 3.10.3 that pass caller-supplied regex patterns to TokenSearcher.findall, Text.findall or RegexpTokenizer
Not fixed by: A wall-clock match timeout does not stop this; compilation runs outside it.
“Confirmed affected range: >= 3.10.0, <= 3.10.3”
What to do
Upgrade to a fixed version: 3.10.4.
Workaround: Validate or reject overly long or group-dense patterns from untrusted input before they reach NLTK regex APIs
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-129229 (NLTK: Compile-time regex DoS in NLTK search/tokenizer sinks: quadratic regex-engine compile bypasses the match-only timeout), 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-129229 (entry last updated 2026-11-19):
Affected:
- nltk nltk: from 3.10.0, fixed in 3.10.4
Fixed versions: 3.10.4.
Conditions (all must be true for the bug to be hit):
- Application passes caller-supplied text as the regex search pattern to TokenSearcher.findall() / Text.findall(), or as the tokenizer pattern to RegexpTokenizer (source: https://github.com/nltk/nltk/security/advisories/GHSA-32p6-cwhc-8r78)
- NLTK version 3.10.0 through 3.10.3 (source: https://github.com/nltk/nltk/security/advisories/GHSA-32p6-cwhc-8r78)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
Workaround: Validate or reject overly long or group-dense patterns from untrusted input before they reach NLTK regex APIs (source: https://github.com/nltk/nltk/security/advisories/GHSA-32p6-cwhc-8r78)
CISA KEV: CVE-2026-129229 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129229 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-32p6-cwhc-8r78
- https://github.com/nltk/nltk/pull/3895
- https://github.com/nltk/nltk/commit/002bcf714ef8cb8baf94436f4be73e5516914412
- 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-129229
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-129229"}.Affected versions
- nltk nltkFrom 3.10.0 · fixed in 3.10.4
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- 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
- Would score about 30 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · nltk/nltk · Advisory GHSA-32p6-cwhc-8r78 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129229 |
| Record | NVD · CVE-2026-129229 |
| Other links 3 | |
| Repository | GitHub · nltk/nltk · Pull request #3895 |
| Repository | GitHub · nltk/nltk · Commit 002bcf71 |
| Repository | GitHub · nltk/nltk · Release v3.10.4 |
Questions about CVE-2026-129229
Is CVE-2026-129229 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 small crafted regex pattern with many empty capturing groups can use a lot of CPU while NLTK compiles it, before the match-only timeout applies, which can tie up worker cores. The advisory states no confidentiality or integrity impact.
Source: github.com
Which versions are affected by CVE-2026-129229?
nltk: from 3.10.0 before 3.10.4.
Source: cve.now feed data
Am I affected, and how do I check?
Affected versions are NLTK 3.10.0 through 3.10.3, in setups where untrusted text is passed as the search pattern to TokenSearcher.findall() or Text.findall(), or as the tokenizer pattern to RegexpTokenizer. Check the installed NLTK version with pip show nltk to see whether it falls in that range.
Source: github.com
How do I fix CVE-2026-129229?
Upgrade NLTK to 3.10.4, which is the listed fixed version. As an interim mitigation, validate or reject overly long or group-dense patterns from untrusted input before they reach NLTK regex APIs.
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-129222Natural Language Toolkit (NLTK): Uncontrolled recursion (crash DoS) in DependencyGraph.tree()/triples()
- 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.