This entry duplicated another and was withdrawn in its favour.
Superseded by ETK-2026-1472.
ETK-2026-107Zero's internal tracking ID, independent of the CVE number.
withdrawndescription
NLTK WekaClassifier accepts model file paths without applying its path-containment checks in affected releases, including 3.10.3. An attacker who can control a model path in an application using this wrapper may cause Weka to write outside approved data directories or probe a chosen file through model loading, even when path enforcement is enabled.
mitigation
Do not permit untrusted users or workflows to select WekaClassifier model paths; enforce an application-level allowlist rooted in approved NLTK data directories. Apply the upstream WekaClassifier path-validation patch when building from source, and track NLTK for the first release that includes it.
outcome
No artifact: an exploit or check was attempted but could not be produced at this moment.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
No signals recorded for this entry yet.
this entry in the feed
GET /api/v1/feed/ETK-2026-107
{ "etk_id": "ETK-2026-107", "cve_id": null, "display_id": "ETK-2026-107", "ghsa_id": null, "euvd_id": null, "status": "retired", "anchor_state": "awaiting_cve", "title": "Path validation bypass in NLTK WekaClassifier", "summary": "NLTK WekaClassifier accepts model file paths without applying its path-containment checks in affected releases, including 3.10.3. An attacker who can control a model path in an application using this wrapper may cause Weka to write outside approved data directories or probe a chosen file through model loading, even when path enforcement is enabled.", "mitigation": "Do not permit untrusted users or workflows to select WekaClassifier model paths; enforce an application-level allowlist rooted in approved NLTK data directories. Apply the upstream WekaClassifier path-validation patch when building from source, and track NLTK for the first release that includes it.", "vendor": "pip", "product": "nltk", "affected": [ { "affected_notes": [], "affected_ranges": [ "<= 3.10.3" ], "ecosystem": "pip", "fixed_versions": [], "package_name": "nltk", "purl": "pkg:pypi/nltk" } ], "cwes": [ 22 ], "cvss_score": 8.6, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L", "epss_score": null, "epss_percentile": null, "epss_asof": null, "automation": "deterministic", "check": false, "check_confidence_basis": null, "exploit": false, "pipeline_minutes": null, "t0_at": null, "signals": {} }
published 2026-09-30 12:15Z
last change 2026-10-13 15:25Z
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.