Medium

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

  • Disclosed: 19.11.2026
  • Updated: 20.11.2026 01:17

Root Cause

The semantic-logic type parser read_type (nltk/sem/logic.py:866) recurses on both halves of every <a,b> complex type (nltk/sem/logic.py:882-884) with no depth or length bound — only an isinstance assertion and a parenthesis-balance assertion. The LogicParser.MAX_PARSE_DEPTH guard (nltk/sem/logic.py:107,294) protects the expression parser but never runs on the read_type path, which is reached directly by the public Type.fromstring classmethod and by signature-string type checking.

Impact

An application that parses an untrusted type string, or type-checks an expression against an attacker-influenced signature, aborts with an unhandled RecursionError, terminating the affected operation or request worker (denial of service, CWE-674). The recursion is pure Python, yielding a catchable RecursionError rather than memory corruption or code execution. Confidentiality and integrity are unaffected. Exposure is narrower than a general-purpose parser because the input must reach a type-string or signature parameter.

Attack Chain

  1. The application calls nltk.sem.logic.Type.fromstring(s) (nltk/sem/logic.py:736) — or Expression.typecheck(signature) / Expression.fromstring(expr, type_check=True, signature=...), which reach read_type for each type-string signature value (nltk/sem/logic.py:1080) — with a deeply nested type string such as "<" * n + "e,e" + ">" * n.
  2. Type.fromstring passes the string straight to read_type with no length or depth check (only assertions on type and parenthesis balance).
  3. read_type recurses on both halves of each <a,b> level, consuming one stack frame per nesting level; the MAX_PARSE_DEPTH guard on the separate LogicParser class does not execute here.
  4. Once the depth exceeds the interpreter recursion limit, an unhandled RecursionError propagates out of the public API.

Bypass Evidence

Running the shipped read_type/ComplexType/Type source verbatim at the default recursion limit: depth 5 parses cleanly to a ComplexType (both assertions satisfied at every level), while depth 5000 raises an unhandled RecursionError. The clean shallow parse shows the failure is depth-driven rather than an assertion failure. A code review confirms the MAX_PARSE_DEPTH bound lives on the LogicParser class and is not applied to read_type, whose own module docstring for that guard explicitly names uncontrolled recursion (CWE-674) as the risk it addresses.

Suggested Fix

Apply a recursion-depth bound to read_type (a depth argument raising a bounded ValueError past a configurable maximum), matching the intent of the existing LogicParser.MAX_PARSE_DEPTH guard so that both the expression and type-string paths are protected.

Reported by pi (GitHub: @manus-pi).

Fix status (2026-09-28)

Status: MERGED on develop (unreleased; v3.10.3 of 2026-08-12 predates the fix).

PR: #3885 "Bound recursion depth in parsers and traversal helpers" (ekaf), merged 2026-09-11, merge commit e521ecafc on develop.

Fix commit: 2f4f0d47e (nltk/sem/logic.py: read_type is bounded by LogicParser.MAX_PARSE_DEPTH) with a8036c5e7 (fixes a NameError in that bound).

Probe: nltk/test/unit/security_probes/ghsa_w3pv_xfw4_ghr7.py (added in 2a6704952 on that PR); verdict on develop 2fa3f48fe: FIXED (bounded (LogicalExpressionException)).

Release: none yet; no release tag contains e521ecafc.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Python (PyPI) nltk < 3.10.4 3.10.4

References

CVSS score 5.3/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Weakness (CWE)
CWE-674
Platform
Python (PyPI)
Package
nltk
Disclosed
19.11.2026
Updated
20.11.2026 01:17

Sources and licenses

OSV / GitHub Advisory Database - GHSA-w3pv-xfw4-ghr7 - CC BY 4.0

Vulnerability history: nltk

All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (79) in the archive
Total entries
79
First → latest
08.2019 11.2026
Without a fix
5
Exploited in attacks
0

Severity breakdown

  • Critical 5
  • High 41
  • Medium 31
  • Low 2

Disclosures per year

  1. 2019: 1
  2. 2020: 0
  3. 2021: 2
  4. 2022: 1
  5. 2023: 0
  6. 2024: 1
  7. 2025: 0
  8. 2026: 74
Severity:
  1. NLTK: Uncontrolled recursion in semantic-logic type parser causes denial of service via nested type strings this entry
    Medium · 5.3 CVE-2026-129226 < 3.10.4 3.10.4
  2. High CVE-2026-79674 < 3.10.3 3.10.3
Show more (20) Showing 20 of 47

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.