Skip to main content
Menu
CVEs

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.

CVE-2026-128139Published November 19, 2026, updated

7.5HighCNA
Exploited
No known exploitation
Fix
Fixed in 3.10.4
Who is exposed
Not reported

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

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. 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.

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.

“affected : PyPI nltk >= 3.6”

github.com

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-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"}.

Affected versions

cve.now Index

25Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.5/10CVSS 7.5
  • 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

Evidence 5

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · nltk/nltk · Advisory GHSA-j8g8-j4j7-8j54
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-128139
RecordNVD · CVE-2026-128139
Other links 2
RepositoryGitHub · nltk/nltk · Commit 9cacbb95
RepositoryGitHub · nltk/nltk · Release v3.10.4

Questions about CVE-2026-128139

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: cve.now feed data

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: github.com

Which versions are affected by CVE-2026-128139?

nltk: from 3.6 before 3.10.4.

Source: cve.now feed data

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: github.com

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: github.com

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