CVE-2026-126298

validatedZero produced an exploit or a check.

GHSA-6665-2vj3-h76r ↗EUVD-2026-125223 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+14h32mkevAttacks confirmed in the real world.
pip nltk <= 3.10.3
fixed in 3.10.4
ETK-2026-4438Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:pypi/nltk
+14h44mTTV
8mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0hpublic poc+14h32mcheck available+14h44magent stopped
0
+3h
+6h
+9h
+12h

description

NLTK versions through 3.10.3 can consume excessive CPU while normalizing parse trees to Chomsky Normal Form. An attacker can cause processing delays or block a worker by supplying a tree with a very large number of children, if the application accepts attacker-influenced trees and invokes the default normalization path.

mitigation

Upgrade nltk to version 3.10.4 or later. Until upgrading, reject or cap unusually wide untrusted trees before normalization and isolate the work with CPU or time limits.

fixed in 3.10.4

check
available
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
8m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-13 09:36Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+14h32m
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual check: a technique exists and was validated, but no deterministic check could cover this one.

source signals

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

  1. 2026-11-13 09:36Z
    ghsa: trigger signal, started the run
  2. 2026-11-13 09:36Z
    public poc, published 2026-11-14 00:07Z
  3. 2026-11-13 09:36Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4438",
  "cve_id": "CVE-2026-126298",
  "display_id": "CVE-2026-126298",
  "ghsa_id": "GHSA-6665-2vj3-h76r",
  "euvd_id": "EUVD-2026-125223",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Quadratic CPU denial of service in NLTK tree normalization",
  "summary": "NLTK versions through 3.10.3 can consume excessive CPU while normalizing parse trees to Chomsky Normal Form. An attacker can cause processing delays or block a worker by supplying a tree with a very large number of children, if the application accepts attacker-influenced trees and invokes the default normalization path.",
  "mitigation": "Upgrade nltk to version 3.10.4 or later. Until upgrading, reject or cap unusually wide untrusted trees before normalization and isolate the work with CPU or time limits.",
  "vendor": "pip",
  "product": "nltk",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 3.10.3"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "3.10.4"
      ],
      "package_name": "nltk",
      "purl": "pkg:pypi/nltk"
    }
  ],
  "cwes": null,
  "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": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 8.420537833333333,
  "t0_at": "2026-11-13T09:36:27.213000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-14T00:20:23.325427+00:00",
      "days": 0.6138438938310186,
      "is_lower_bound": false,
      "measured_at": "2026-11-13T09:36:27.213000+00:00",
      "url": null
    },
    "public_poc": {
      "at": "2026-11-14T00:07:59+00:00",
      "days": 0.6052290162037037,
      "is_lower_bound": false,
      "measured_at": "2026-11-13T09:36:27.213000+00:00",
      "url": "https://github.com/advisories/GHSA-r53h-rw34-8h97"
    },
    "trigger_signal": {
      "at": "2026-11-13T09:36:27.213000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-13T09:36:27.213000+00:00",
      "url": "https://github.com/advisories/GHSA-r53h-rw34-8h97"
    }
  }
}

published 2026-11-14 00:11Z
last change 2026-11-14 07:07Z

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.