CVE-2026-128139

waiting for further signalsZero needs more public information before it can validate it.

GHSA-j8g8-j4j7-8j54 ↗

no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
pip nltk 3.6 - 3.10.3
fixed in 3.10.4
CWE-400 Uncontrolled Resource Consumption
ETK-2026-4528Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:pypi/nltk
3d 04h 24msince last run
9mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
trigger signal −3.4dwaiting for further signals−3.2d
−3d
−2d
−1d
0

description

NLTK's XMLCorpusView can consume disproportionate CPU time while reading XML corpus files, affecting nltk versions from 3.6 through 3.10.3. An attacker can cause a denial of service if they can induce an application to process a crafted, well-formed XML corpus containing a large comment or CDATA section.

mitigation

Upgrade nltk to version 3.10.4 or later. Until upgrading, do not process untrusted XML corpus files and enforce input-size limits where such processing is required.

fixed in 3.10.4

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
9m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-15 12:34Z

this entry in the feed

GET /api/v1/feed/CVE-2026-128139

{
  "etk_id": "ETK-2026-4528",
  "cve_id": "CVE-2026-128139",
  "display_id": "CVE-2026-128139",
  "ghsa_id": "GHSA-j8g8-j4j7-8j54",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Quadratic denial of service in NLTK XMLCorpusView",
  "summary": "NLTK's XMLCorpusView can consume disproportionate CPU time while reading XML corpus files, affecting nltk versions from 3.6 through 3.10.3. An attacker can cause a denial of service if they can induce an application to process a crafted, well-formed XML corpus containing a large comment or CDATA section.",
  "mitigation": "Upgrade nltk to version 3.10.4 or later. Until upgrading, do not process untrusted XML corpus files and enforce input-size limits where such processing is required.",
  "vendor": "pip",
  "product": "nltk",
  "affected": [
    {
      "affected_notes": [
        "3.6 - 3.10.3"
      ],
      "affected_ranges": [],
      "ecosystem": "pip",
      "fixed_versions": [
        "3.10.4"
      ],
      "package_name": "nltk",
      "purl": "pkg:pypi/nltk"
    }
  ],
  "cwes": [
    400
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 8.902580316666667,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-11-15T12:34:27+00:00",
      "days": -3.386147480787037,
      "is_lower_bound": true,
      "measured_at": "2026-11-18T21:50:30.219478+00:00",
      "url": "https://github.com/nltk/nltk/security/advisories/GHSA-j8g8-j4j7-8j54"
    }
  }
}

published 2026-11-15 17:32Z
last change 2026-11-18 21:43Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.