CVE-2026-129226
Nested type declarations could crash an NLTK semantic parser
NLTK project · Natural Language Toolkit · semantic logic parser
First documented disclosure · Review checkpoint
Summary
A program parsing external semantic type declarations could lose a worker to excessively nested input.
Severity and exploitation evidence
Medium · 5.3/10 · CVSS 3.1. Severity source.
Exploitation not established: The NLTK advisory describes the vulnerability and its preconditions. The reviewed sources identify no malicious use.
Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.
How the weakness works
The semantic type parser recursively processed component types without a nesting bound.
Conditions required
An application accepts external semantic type strings.
Potential impact
A type declaration could interrupt a parsing job by exhausting its call stack.
Affected versions and configurations
<= 3.10.3
Fix and mitigation status
3.10.4.
Practical next steps
Upgrade to NLTK 3.10.4 or a later fixed release.
Operating lesson
Limit complexity on type declarations as well as expressions.
Evidence and limits
The issue-specific patch was public by 2026-09-11. The fixed release shipped October 21. The November 15 maintainer advisory supplies the identifier and affected versions. This is a historical addition.
Sources
- NLTK public patch for semantic logic parser
Primary source ·
- NLTK 3.10.4 release notes
Primary source ·
- NLTK advisory GHSA-w3pv-xfw4-ghr7
Primary source ·