NLTK: Untrusted search path
Affects nltkSource GCVE Database
Not known to be exploited · CVSS 7.3 High : upgrade to 3.10.4 soon.
Data as of 20 Nov 2026, 00:28 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 7.3 |
|---|
- Patch
- Available – fixed in 3.10.4
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade nltk to 3.10.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PyPInltk | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in NLTK version 3.10.4 and later, which rejects relative binary_location paths for prover9 and mace4, enforcing absolute-only binary paths. Users should upgrade to version 3.10.4 or later to remediate this vulnerability. Until upgrading, avoid configuring prover9 or mace4 with relative binary_location paths and ensure that untrusted users cannot write to directories from which these binaries are resolved.
Description
NLTK versions up to 3.10.3 have a vulnerability in the prover9 and mace4 configuration that allows local code execution when a relative binary_location is used. The issue arises because the code accepts relative paths for the prover9/mace4 binaries without validating that they are absolute paths, leading to execution of attacker-planted binaries in the current working directory. This flaw is due to missing path validation that other similar components in NLTK enforce. A fix is available in version 3.10.4, which rejects relative binary locations and enforces absolute-only paths.
References
- github.com/nltk/nltk/security/advisories/GHSA-cc5r-64rf-75hg (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-129234 (opens in a new tab)
- github.com/nltk/nltk/pull/3887 (opens in a new tab)
- github.com/nltk/nltk/commit/4ca190b744ec72500c4c8a8259aece7792a46877 (opens in a new tab)
- github.com/nltk/nltk/commit/992884a02f6fb5180a992ed12d20103b4b5cb8a0 (opens in a new tab)
- github.com/nltk/nltk/commit/d4f0309bb8649f77e88c2c435e5fa31e6c5ab225 (opens in a new tab)
- github.com/nltk/nltk/commit/f0a75c66506977c0f683281c0f5275dbfbaee3b2 (opens in a new tab)
- github.com/nltk/nltk (opens in a new tab)
- github.com/nltk/nltk/releases/tag/v3.10.4 (opens in a new tab)