CVE-2026-129222

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

GHSA-rh8m-wqhc-qmrf ↗

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.10.3
fixed in 3.10.4
CWE-674 Uncontrolled Recursion
ETK-2026-4538Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:pypi/nltk
cvss7.0ethiack provisional
3d 03h 04msince last run
14mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0dwaiting for further signals+0.2d
0
+1d
+2d
+3d

description

NLTK DependencyGraph traversal is affected by uncontrolled recursion when processing deeply nested dependency parses. An attacker who can supply dependency-parse input to an application and cause it to call tree() or triples() can crash the affected worker, request handler, or script.

mitigation

Upgrade NLTK to version 3.10.4. Until the upgrade is deployed, reject or limit unusually deep untrusted dependency-parse inputs and avoid invoking DependencyGraph traversal on them.

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.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
14m
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:30Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4538",
  "cve_id": "CVE-2026-129222",
  "display_id": "CVE-2026-129222",
  "ghsa_id": "GHSA-rh8m-wqhc-qmrf",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Uncontrolled recursion in NLTK DependencyGraph traversal",
  "summary": "NLTK DependencyGraph traversal is affected by uncontrolled recursion when processing deeply nested dependency parses. An attacker who can supply dependency-parse input to an application and cause it to call tree() or triples() can crash the affected worker, request handler, or script.",
  "mitigation": "Upgrade NLTK to version 3.10.4. Until the upgrade is deployed, reject or limit unusually deep untrusted dependency-parse inputs and avoid invoking DependencyGraph traversal on them.",
  "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": [
    674
  ],
  "cvss_score": 7,
  "cvss_src": "ethiack_provisional",
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 14.108805983333333,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-11-15T12:30:10+00:00",
      "days": -3.3699506719328705,
      "is_lower_bound": true,
      "measured_at": "2026-11-18T21:22:53.786140+00:00",
      "url": "https://github.com/nltk/nltk/security/advisories/GHSA-rh8m-wqhc-qmrf"
    }
  }
}

published 2026-11-15 18:35Z
last change 2026-11-18 21:09Z

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.