Skip to main content
Menu
CVEs

NLTK denial of service in semantic-logic type parser

CVE-2026-129226EUVD-2026-130432Published November 19, 2026, updated

5.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 3.10.4
Who is exposed
Not reported

Summary

NLTK, the Natural Language Toolkit Python library, is affected by a bug in its semantic-logic type parser. A remote attacker who can supply a deeply nested type string, without logging in, can crash the worker process running it, causing a denial of service.

Written by a model

Original description

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.

What to do

Upgrade to a fixed version: 3.10.4.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-129226 (NLTK: Uncontrolled recursion in semantic-logic type parser causes denial of service via nested type strings), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129226 (entry last updated 2026-11-19):
Affected:
- nltk nltk: fixed in 3.10.4
Fixed versions: 3.10.4.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129226 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129226 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/nltk/nltk/security/advisories/GHSA-w3pv-xfw4-ghr7
- https://github.com/nltk/nltk/pull/3885
- https://github.com/nltk/nltk/commit/2f4f0d47e2c452c89cabc2a5f761332d51066ea8
- https://github.com/nltk/nltk/commit/a8036c5e7f820ac09c96b969d6e7f19bfa6e6aeb
- https://github.com/nltk/nltk/releases/tag/v3.10.4
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129226
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129226"}.

Affected versions

cve.now Index

25Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.3/10CVSS 5.3
  • No patch0/5No signal

What would change the score

  • Would score about 70 if added to CISA KEV
  • Would score about 65 if CISA's SSVC rates exploitation active
  • Would score about 30 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Evidence 7

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · nltk/nltk · Advisory GHSA-w3pv-xfw4-ghr7
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-129226
RecordNVD · CVE-2026-129226
Other links 4
RepositoryGitHub · nltk/nltk · Pull request #3885
RepositoryGitHub · nltk/nltk · Commit 2f4f0d47
RepositoryGitHub · nltk/nltk · Commit a8036c5e
RepositoryGitHub · nltk/nltk · Release v3.10.4

Questions about CVE-2026-129226

Is CVE-2026-129226 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-129226?

nltk: before 3.10.4.

Source: cve.now feed data

How do I fix CVE-2026-129226?

Upgrade to a fixed version: 3.10.4.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.