Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
NLTK versions before 3.10.1 are vulnerable to denial of service in TweetTokenizer, caused by catastrophic regular expression backtracking when tokenizing crafted input. An attacker who can submit text to a service that applies TweetTokenizer or casual_tokenize can stall that request for seconds to minutes of CPU time, with no authentication needed. Upgrade to NLTK 3.10.1 or later, which bounds the repetition in the affected pattern.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 8.7 | High | 4.0 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N | CNA (VulnCheck) |
- CISA KEV Not listed.
- EPSS 0.0074, the 55th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:10 UTC First seen by agentprime
- 31 Oct 2026, 14:10 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-qx2g-xrx7-vfh8
- OSV: GHSA-qx2g-xrx7-vfh8
- nvd.nist.gov/vuln/detail/CVE-2026-72818
- github.com/nltk/nltk/issues/3704
- github.com/nltk/nltk/pull/3701
- github.com/nltk/nltk/commit/e092ed52eccae642304448bffc8d23cb301f85c1
- github.com/nltk/nltk
- github.com/nltk/nltk/blob/3.9.4/nltk/tokenize/casual.py
- github.com/nltk/nltk/releases/tag/v3.10.1
- www.vulncheck.com/advisories/nltk-tweettokenizer-url-pattern-backtracks-catastrophically-on-naked-domain-like-input