NLTK local code execution in prover9 search path
Only affects NLTK setups that configure prover9 or mace4 with a relative binary_location. Fixed in 3.10.4.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.10.4
- Who is exposed
- Specific setups only
Summary
NLTK, the Natural Language Toolkit, has an untrusted search path flaw in its prover9 and mace4 configuration that lets a local attacker run code with the privileges of the user who runs it. To exploit it, an attacker with low-privilege local access must plant a prover9 or mace4 program in the working directory and get a user to act, because NLTK then runs that planted program when a relative binary location is used.
Written by a model
Original description
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.
Who should check
Teams running NLTK (nltk on pip) 3.10.3 or earlier that call Prover9, Mace or config_prover9 with a relative binary_location on shared or writable working directories.
“Affected versions <= 3.10.3”
What to do
Check whether your setup matches what the bug needs.
Application is configured with a relative binary_location for prover9/mace4 (config_prover9 or config_mace). Attacker can write to the resolved working directory and plant prover9 or mace4 there.Upgrade to a fixed version: 3.10.4.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129234 (NLTK: Untrusted search path in prover9/mace4 config allows local code execution via relative binary_location), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129234 (entry last updated 2026-11-19):
Affected:
- nltk nltk: fixed in 3.10.4
Fixed versions: 3.10.4.
Conditions (all must be true for the bug to be hit):
- Application is configured with a relative binary_location for prover9/mace4 (config_prover9 or config_mace). (source: https://github.com/nltk/nltk/security/advisories/GHSA-cc5r-64rf-75hg)
- Attacker can write to the resolved working directory and plant prover9 or mace4 there. (source: https://github.com/nltk/nltk/security/advisories/GHSA-cc5r-64rf-75hg)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: local access, low-privilege login, a user action.
CISA KEV: CVE-2026-129234 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129234 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/nltk/nltk/security/advisories/GHSA-cc5r-64rf-75hg
- https://github.com/nltk/nltk/pull/3887
- https://github.com/nltk/nltk/commit/4ca190b744ec72500c4c8a8259aece7792a46877
- https://github.com/nltk/nltk/commit/992884a02f6fb5180a992ed12d20103b4b5cb8a0
- https://github.com/nltk/nltk/commit/d4f0309bb8649f77e88c2c435e5fa31e6c5ab225
- https://github.com/nltk/nltk/commit/f0a75c66506977c0f683281c0f5275dbfbaee3b2
- https://github.com/nltk/nltk/releases/tag/v3.10.4
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129234
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129234"}.Affected versions
- nltk nltkfixed in 3.10.4
cve.now Index
- Exploitation0/40No signal
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.3/10CVSS 7.3, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Evidence 9
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · nltk/nltk · Advisory GHSA-cc5r-64rf-75hg |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129234 |
| Record | NVD · CVE-2026-129234 |
| Other links 6 | |
| Repository | GitHub · nltk/nltk · Pull request #3887 |
| Repository | GitHub · nltk/nltk · Commit 4ca190b7 |
| Repository | GitHub · nltk/nltk · Commit 992884a0 |
| Repository | GitHub · nltk/nltk · Commit d4f0309b |
| Repository | GitHub · nltk/nltk · Commit f0a75c66 |
| Repository | GitHub · nltk/nltk · Release v3.10.4 |
Questions about CVE-2026-129234
Is CVE-2026-129234 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
Prover9 and Mace configuration accepts a relative binary_location, so a local attacker who can place a planted ./prover9 or ./mace4 in the resolved working directory can get code run as the invoking user.
Source: github.com
Which versions are affected by CVE-2026-129234?
nltk: before 3.10.4.
Source: cve.now feed data
Am I affected, and how do I check?
Affected are NLTK versions before 3.10.4 where the application sets a relative binary_location through config_prover9 or config_mace. To check, run pip show nltk or print nltk.__version__ and review the calls to config_prover9 or config_mace for a relative path.
Source: github.com
How do I fix CVE-2026-129234?
Upgrade NLTK to 3.10.4 or later, which is the listed fixed version.
Source: github.com
Related
- CVE-2026-128138NLTK incomplete fix: additional JVM/JAR sandbox bypass through unvalidated launcher tokens in java() command arguments
- CVE-2026-128134NLTK dot2img runs Graphviz 'dot' without the trusted-exec chokepoint, enabling local code execution via a writable PATH element
- CVE-2026-129223Natural Language Toolkit (NLTK): Uncontrolled recursion (crash DoS) in Synset.tree()/acyclic_tree() via WordNet relation traversal
- CVE-2026-128139NLTK: XMLCorpusView comment and CDATA parsing permits quadratic CPU denial of service
- CVE-2026-129222Natural Language Toolkit (NLTK): Uncontrolled recursion (crash DoS) in DependencyGraph.tree()/triples()
- CVE-2026-129229NLTK: Compile-time regex DoS in NLTK search/tokenizer sinks: quadratic regex-engine compile bypasses the match-only timeout
No corrections so far. Something wrong on this page? Report an error.