cve.bz

CVE-2026-129226 NLTK: Uncontrolled recursion in semantic-logic type parser causes denial of service via nested type strings

5.3 mediumEPSS 0.5%Fix available

Medium (5.3) in nltk nltk. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in nltk 3.10.4.

On this page
NLTK (Natural Language Toolkit) is a suite of open source Python modules, data sets, and tutorials supporting research and development in Natural Language Processing. Prior to 3.10.4, the semantic-logic read_type parser recursively processes both halves of nested complex type strings without applying LogicParser.MAX_PARSE_DEPTH. An attacker-controlled type string or signature with excessive nesting can raise RecursionError through Type.fromstring or type-checking entry points and abort the current worker. This issue is fixed in version 3.10.4.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS
0.5% estimated probability of exploitation activity in the next 30 days; 42nd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-11-19. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-674 Uncontrolled Recursion
Published
Modified
Assigned by
GitHub_M (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • nltk (PyPI): fixed in 3.10.4

Ask an AI about this CVE

Show the promptExplain CVE-2026-129226 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-129226?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-129226?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-129226 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
nltk< 3.10.4

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-w3pv-xfw4-ghr7PyPInltk<3.10.43.10.4

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • googlesky/CVE-2026-129226 Harbor Check: matches CVE 0 stars, Python, created
    NLTK <=3.10.3: the semantic-logic type parser read_type recursed on both halves of every <a,b> with no depth bound — MAX_PARSE_DEPTH never …

Attack patterns (CAPEC)

  • CAPEC-230 Serialized Data with Nested Payloads Likelihood: Medium · Severity: High
  • CAPEC-231 Oversized Serialized Data Payloads Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON