PoC Monitor
← All CVEs
CVE-2026-72818published 20 Aug 2026 21:57 UTCData: JSON · API

NLTK

NLTK TweetTokenizer URL Pattern Backtracks Catastrophically on Naked-Domain-Like Input

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.7high · scored by CNA · CWE-1333
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

nltk nltk
  • < 3.10.1

Fixed in 3.10.1

Mitigation

Upgrade nltk to 3.10.1 or later.

References

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published20 Aug 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.