SteppingRecursiveDescentParser.parse() with ambiguous or self-embedding grammars · NLTK: Unbounded CPU consumption
Affects safetySource GCVE Database
Not known to be exploited · CVSS 8.7 High : upgrade to 3.8.1_3 soon.
Data as of 18 Nov 2026, 18:04 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 8.7 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 7.5 |
- Patch
- Available – fixed in 3.8.1_3
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 17 Nov 2026.
What to do
Upgrade safety to 3.8.1_3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewsafetypkg:brew/safetyOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in NLTK version 3.8.1_3. Users should upgrade to this version or later to ensure the SteppingRecursiveDescentParser enforces time bounds on parsing operations. Until upgraded, avoid using SteppingRecursiveDescentParser on untrusted or attacker-controlled grammars and inputs. The base RecursiveDescentParser with max_time parameter can be used as a safer alternative for parsing untrusted inputs.
Description
The NLTK library's SteppingRecursiveDescentParser.parse() method performs an unbounded top-down search on ambiguous or self-embedding grammars without enforcing any time or step limits. This allows an attacker who can influence the grammar and input tokens to cause the parser to consume CPU indefinitely, resulting in a denial of service. The base RecursiveDescentParser enforces a max_time limit, but the stepping subclass overrides parsing logic and does not support or enforce this limit. This vulnerability affects NLTK versions from 3.3.1 up to but not including 3.8.1_3 and has been fixed in version 3.8.1_3.
References
- github.com/nltk/nltk/security/advisories/GHSA-8fx7-8jr8-84rv (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-126303 (opens in a new tab)
- github.com/nltk/nltk/pull/3895 (opens in a new tab)
- github.com/nltk/nltk/commit/e20c40e26ec9306de885703f6e53250695f1f49b (opens in a new tab)
- github.com/nltk/nltk (opens in a new tab)
- github.com/nltk/nltk/releases/tag/v3.10.4 (opens in a new tab)
- vulncheck.com/advisories/nltk-before-3.10.4-denial-of-service-via-steppingrecursivedescentparser-parse (opens in a new tab)