Skip to main content
CVE-2026-129234VulnerabilityPublished

NLTK: Untrusted search path

Affects nltkSource GCVE Database

0
Compare
Authoritative record:CVE-2026-129234· High 7.3

Not known to be exploited · CVSS 7.3 High : upgrade to 3.10.4 soon.

Data as of 20 Nov 2026, 00:28 UTC

CVSS 3.1 base score
7.3High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.17.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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
PyPInltkAffected
  • <3.10.4
Fixed in
  • 3.10.4

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

Community reviews

Loading reviews…