CVE-2026-129229

NLTK could exhaust CPU before a tokenizer or search timeout began

NLTK project · Natural Language Toolkit · tokenization and text search

First documented disclosure · Review checkpoint

Summary

An external search or tokenization pattern could consume substantial CPU before the configured match timeout applied.

Severity and exploitation evidence

High · 7.5/10 · CVSS 3.1. Severity source.

Exploitation not established: The NLTK advisory describes the vulnerability and its preconditions. The reviewed sources identify no malicious use.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

Regular-expression compilation occurred before the timeout for matching took effect.

Conditions required

An application accepts an external search or tokenizer expression.

Potential impact

Compiling one expression could monopolize a processing worker and delay other requests.

Affected versions and configurations

>= 3.10.0, <= 3.10.3

Fix and mitigation status

3.10.4.

Practical next steps

Upgrade to NLTK 3.10.4 or a later fixed release.

Operating lesson

Apply resource limits to compilation as well as matching.

Evidence and limits

The issue-specific patch was public by 2026-08-31. The fixed release shipped October 21. The November 15 maintainer advisory supplies the identifier and affected versions. This is a historical addition.

Sources