CVE-2026-72818
Description
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
nltkPyPI | < 3.10.1 | 3.10.1 |
Affected products
4- osv-coords3 versions
< 2.7.3-r27+ 2 more
- (no CPE)range: < 2.7.3-r27
- (no CPE)range: < 0.11.3-r1
- (no CPE)range: < 0.11.3-r1
Patches
Vulnerability mechanics
References
8- github.com/advisories/GHSA-qx2g-xrx7-vfh8ghsaADVISORY
- nvd.nist.gov/vuln/detail/CVE-2026-72818ghsaADVISORY
- github.com/nltk/nltk/blob/3.9.4/nltk/tokenize/casual.pynvdWEB
- github.com/nltk/nltk/commit/e092ed52eccae642304448bffc8d23cb301f85c1ghsaWEB
- github.com/nltk/nltk/issues/3704nvdWEB
- github.com/nltk/nltk/pull/3701ghsaWEB
- github.com/nltk/nltk/releases/tag/v3.10.1nvdWEB
- www.vulncheck.com/advisories/nltk-tweettokenizer-url-pattern-backtracks-catastrophically-on-naked-domain-like-inputnvdWEB
News mentions
1- NLTK: Thirteen Path Traversal, RCE, and DoS Vulnerabilities Disclosed TogetherVypr Intelligence · Aug 22, 2026