Skip to main content
VulnerabilityPublished Updated

CVE-2026-126301: NLTK · Quadratic CPU exhaustion in LegalitySyllableTokenizer.tokenize via unguarded onset reversal loop

Affects acronymSource GCVE Database

0
Compare
Authoritative record:CVE-2026-126301· Medium 6.9

Not known to be exploited · CVSS 6.9 Medium : upgrade to 2.0.0_6 when convenient.

Data as of 17 Nov 2026, 19:05 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.06.9
CNA (VulnCheck)CVSS 3.15.3
Patch
Available – fixed in 2.0.0_6
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade acronym to 2.0.0_6.

Affected software

ProductAffectedFixed in
Homebrewacronympkg:brew/acronymOther threatsAffected
  • >=2.0.0 <2.0.0_6
Fixed in
  • 2.0.0_6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in version 2.0.0_6 that addresses this issue. Users should upgrade to this fixed version to mitigate the vulnerability. No other mitigations are indicated or required.

Description

The NLTK package's LegalitySyllableTokenizer.tokenize method contains a quadratic CPU exhaustion vulnerability triggered by tokens consisting of long runs of vowels. This flaw causes CPU time to grow with the square of the token length, allowing an attacker controlling input tokens to degrade service availability by saturating a CPU core. The vulnerability does not affect confidentiality or integrity but can cause denial of service or latency degradation. A fix is available in version 2.0.0_6.

References

Community reviews

Loading reviews…