Skip to main content
VulnerabilityPublished Updated

CVE-2026-12876: NLTK · Uncontrolled resource consumption in RecursiveDescentParser via ambiguous or left-recursive grammars

Affects gptlineSource GCVE Database

0
Compare

Mentioned vulnerabilities

Not known to be exploited · CVSS 6.9 Medium : upgrade to 1.0.8_23 when convenient.

Data as of 18 Sep 2026, 01:51 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 1.0.8_23
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 3 Sep 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 1 Nov 2026.

What to do

Upgrade gptline to 1.0.8_23.

Affected software

ProductAffectedFixed in
Homebrewgptlinepkg:brew/gptlineOther threatsAffected
  • >=1.0.8 <1.0.8_23
Fixed in
  • 1.0.8_23

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 for this vulnerability. Users should update to a fixed version of the affected software to prevent denial of service via crafted grammars or inputs. Avoid running RecursiveDescentParser on grammars or inputs from untrusted sources until patched.

Description

The RecursiveDescentParser and SteppingRecursiveDescentParser components in NLTK can be exploited by crafted ambiguous or left-recursive grammars to cause unbounded CPU consumption or stack exhaustion, resulting in denial of service. This affects applications that parse grammars or inputs from untrusted sources. There is no impact on confidentiality or integrity, only on availability of the affected process. A patch is available to address this issue.

References

Community reviews

Loading reviews…