NLTK · GHSA-x4p7-2mv3-x7px · Package
NO FIX YET · SEE WHAT TO DO
NLTK's LegalitySyllableTokenizer uses a loop that does quadratic work on long all-vowel tokens. An attacker who can supply such text can tie up CPU and deny service to code that syllabifies text.
first public Nov 13, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Applications that pass untrusted text to NLTK's LegalitySyllableTokenizer are exposed, since a long all-vowel token triggers the quadratic loop. Batch jobs run on trusted corpora, or code that never calls this tokenizer, can skip it. The advisory is withdrawn and points to GHSA-gpwc-27cw-rh9r, so check that record for the authoritative scope.
Not affected if tokenizer-unused, trusted-input-only
Who cares nltk, python, web-services
pip show nltknltk 3.10.4 or later, per the affected range in this advisoryThis advisory has been withdrawn because it is a duplicate of GHSA-gpwc-27cw-rh9r. This link is maintained to preserve external references.
NLTK from 3.6 before 3.10.4 contains an algorithmic complexity vulnerability in LegalitySyllableTokenizer.tokenize that allows remote attackers to exhaust CPU by supplying long all-vowel tokens. Attackers can submit a token such as a long run of vowels, causing the unguarded onset reversal loop to perform quadratic work and deny service to syllabification components.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
GitHub Advisory Database, CC-BY 4.0. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.