CVE-2026-72818
HIGHDescription
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.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Exploit Intelligence
Moderate risk: more likely to be exploited than 41% of all known CVEs.
References
Related Vulnerabilities
Other CWE-1333 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2023-3364 | High | 7.5 | 44% | - | Fix |
| CVE-2024-8124 | High | 7.5 | 40% | - | Fix |
| CVE-2024-25126 | Medium | 5.3 | 35% | - | Fix |
| CVE-2024-2651 | Medium | 6.5 | 33% | - | Fix |
| CVE-2021-32837 | High | 7.5 | 29% | - | Fix |
| CVE-2024-2829 | High | 7.5 | 26% | - | Fix |
Common questions
How do I fix CVE-2026-72818?
Upgrade nltk on debian unstable to 3.10.3-1 or later.
Is CVE-2026-72818 being actively exploited?
Not that we know of. CVE-2026-72818 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.51% is the estimated probability that it will be exploited in the next 30 days. That is higher than 41% of all scored CVEs.
How severe is CVE-2026-72818?
CVE-2026-72818 has a CVSS v3 base score of 7.5, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-72818 affect?
Published advisories record a fix for nltk (Debian). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-72818
Markdown
[](https://tridentstack.com/cve/CVE-2026-72818)HTML
<a href="https://tridentstack.com/cve/CVE-2026-72818"><img src="https://tridentstack.com/cve/badge/CVE-2026-72818.svg" alt="CVE-2026-72818"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-21.