CVE-2026-129234 json
NLTK: Untrusted search path in prover9/mace4 config allows local code execution via relative binary_location
published 6d ago modified yesterday also EUVD-2026-130480 , GHSA-cc5r-64rf-75hg
- cvss
- 7.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 13%
- public exploits
- 0
- none known
Summary
NLTK (Natural Language Toolkit) is a suite of open source Python modules, data sets, and tutorials supporting research and development in Natural Language Processing. Prior to 3.10.4, Prover9Parent.config_prover9 and Mace accept a relative binary_location and pass it to find_binary as path_to_bin, disabling the bare-name absolute-path guard. A local attacker who can plant prover9 or mace4 in the resolved working directory can cause subprocess.Popen to execute that binary with the invoking user's privileges. This issue is fixed in version 3.10.4.
Patch / fix
- pypi nltk 3.10.4
- github.com/nltk/nltk@4ca190b commit
- github.com/nltk/nltk@992884a commit
- github.com/nltk/nltk@d4f0309 commit
- github.com/nltk/nltk@f0a75c6 commit
- github.com/nltk/nltk#3887 pull request
- github.com/nltk/nltk/releases/tag/v3.10.4 release
Is CVE-2026-129234 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- yesterday
Exploit prediction
0.23% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-21).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 7.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | nltk | <3.10.4 |
3.10.4 |
Affected products
- nltk nltk
Classification
References
-
github.com
/nltk/nltk/pull/3887
web
-
github.com
/nltk/nltk/commit/4ca190b744ec72500c4c8a8259aece7792a46877
web
-
github.com
/nltk/nltk/commit/992884a02f6fb5180a992ed12d20103b4b5cb8a0
web
-
github.com
/nltk/nltk/commit/d4f0309bb8649f77e88c2c435e5fa31e6c5ab225
web
-
github.com
/nltk/nltk/commit/f0a75c66506977c0f683281c0f5275dbfbaee3b2
web
-
github.com
/nltk/nltk/security/advisories/GHSA-cc5r-64rf-75hg
web, advisory
-
github.com
/nltk/nltk/releases/tag/v3.10.4
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-129234
advisory
-
github.com
/nltk/nltk
package
Sources
- CVE List CVE-2026-129234
- GitHub Advisory GHSA-cc5r-64rf-75hg
- NVD CVE-2026-129234
- Maintainer advisory GHSA-cc5r-64rf-75hg
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of nltk/nltk published their own advisory on GitHub. Reviewed sources take precedence over it.