INCIDENT MAP

Browse / AI Framework and Platform Flaws / CVE-2026-72818

NLTK TweetTokenizer vulnerable to denial of service through catastrophic regex backtracking

CVE-2026-72818 ยท 2026-08-21 high

Class
AI Framework and Platform Flaws (filed by a model that read the advisory)
Technique
Denial of service
Affected
nltk (PyPI)
CVSS
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.7% chance of exploitation in 30 days

How it works, in short

Crafted strings of repeated separators make a tokenizer regex backtrack exponentially, so a few kilobytes of text can stall a worker thread for minutes. (Our summary, written by a model. The source text is below.)

Details

The URLS regular expression in nltk/tokenize/casual.py, compiled into TweetTokenizer.WORD_RE and applied by TweetTokenizer.tokenize, contains a naked-domain branch whose domain-label prefix [a-z0-9]+(?:[.\-][a-z0-9]+)* is unbounded. Input consisting of many alternating label separators can be partitioned in exponentially many ways, and because the branch also requires a trailing top-level domain that such input never supplies, the engine explores those partitions before failing at each offset. A few kilobytes of input therefore consumes seconds to minutes of single-threaded CPU, and the HANG_RE substitution performed before matching does not collapse the pattern. TweetTokenizer is intended for tokenizing untrusted social-media text, so any service that applies it, or the module-level casual_tokenize, to submitted text can be stalled per request without authentication. Version 3.10.1 bounds the label repetition.

References

Source: GitHub Advisory Database, used under CC BY 4.0.