Skip to main content
Menu
CVEs

NLTK local code execution in dot2img via untrusted PATH

Affects NLTK 3.10.3 and earlier on POSIX hosts where a group- or world-writable directory appears on PATH. Fixed in NLTK 3.10.4.

CVE-2026-128134EUVD-2026-125821Published November 13, 2026, updated

7.8HighCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 3.10.4
Who is exposed
Specific setups only

Summary

The NLTK (Natural Language Toolkit) Python library is affected: its `dot2img` function and `DependencyGraph.repr_svg` method run the Graphviz `dot` program without the library's trusted-execution checks. A local attacker with low privileges who can write to a directory on a POSIX victim's PATH can plant or replace `dot`, and that code then runs as the victim when `dot2img` is called or a graph is rendered with `repr_svg`.

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, nltk.parse.dependencygraph.dot2img resolves the Graphviz dot executable through PATH but invokes the resulting absolute executable without routing through spawn_trusted, so resolve_trusted_executable ownership and writability validation and safe_env loader environment scrubbing do not run. A local low-privileged attacker who can write to a directory on a POSIX victim's PATH can plant or replace dot, and code executes as the victim when dot2img is called directly or DependencyGraph.repr_svg renders a graph. The current-working-directory-only bare-name vector is blocked and is not this vulnerability; this issue is the residual writable absolute PATH element bypass after CVE-2026-78680. This issue is fixed in version 3.10.4.

Who should check

Teams running NLTK 3.10.3 or earlier on POSIX hosts, such as Jupyter users rendering dependency graphs, where a group/world-writable directory is on PATH.

Not fixed by: The earlier CVE-2026-78680 fix does not cover dot2img.

“Confirmed affected range: <= 3.10.3”

github.com

What to do

  1. Check whether your setup matches what the bug needs.

    NLTK version 3.10.3 or earlier (affected range <= 3.10.3). POSIX host where a group- or world-writable directory appears on the victim's PATH.
  2. 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-128134 (NLTK dot2img runs Graphviz 'dot' without the trusted-exec chokepoint, enabling local code execution via a writable PATH element), 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-128134 (entry last updated 2026-11-16):
Affected:
- nltk nltk: fixed in 3.10.4
Fixed versions: 3.10.4.
Conditions (all must be true for the bug to be hit):
- NLTK version 3.10.3 or earlier (affected range <= 3.10.3). (source: https://github.com/nltk/nltk/security/advisories/GHSA-7mxv-7h3q-9324)
- POSIX host where a group- or world-writable directory appears on the victim's PATH. (source: https://github.com/nltk/nltk/security/advisories/GHSA-7mxv-7h3q-9324)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, low-privilege login, no user action.
CISA KEV: CVE-2026-128134 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128134 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-7mxv-7h3q-9324
- https://github.com/nltk/nltk/pull/3887
- https://github.com/nltk/nltk/commit/b002a7288c22db86fd6ca2d9526e3f91d6fda797
- 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-128134
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-128134"}.

Affected versions

cve.now Index

29of 100 · methodology v3
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure5/25Specific setups only
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.8/10CVSS 7.8, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 64 if added to CISA KEV
  • Would score about 59 if CISA's SSVC rates exploitation active
  • Would score about 39 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now3 days
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: total

  4. Record last updated

Public exploit activity

10100%0Nov 13Nov 20
  • GitHub PoC repos: 1
  • EPSS: 0.18%

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

Evidence 7

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · nltk/nltk · Advisory GHSA-7mxv-7h3q-9324
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-128134
RecordNVD · CVE-2026-128134
Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
ExploitGitHub · LLCForge/CVE-2026-128134 · Repository
Other links 3
RepositoryGitHub · nltk/nltk · Pull request #3887
RepositoryGitHub · nltk/nltk · Commit b002a728
RepositoryGitHub · nltk/nltk · Release v3.10.4

Questions about CVE-2026-128134

Is CVE-2026-128134 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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

NLTK's dot2img runs the Graphviz 'dot' program without the trusted-execution check. A local, unprivileged user who can write to a group- or world-writable directory on the victim's PATH can get arbitrary code run in the victim's account.

Source: github.com

Which versions are affected by CVE-2026-128134?

nltk: before 3.10.4.

Source: cve.now feed data

Am I affected, and how do I check?

NLTK version 3.10.3 or earlier is affected, on POSIX hosts where a group- or world-writable directory appears on the victim's PATH. To check, print the installed NLTK version and list the directories on PATH, then look at their write permissions.

Source: github.com

How do I fix CVE-2026-128134?

Upgrade NLTK to 3.10.4, which is the first fixed version.

Source: github.com

No corrections so far. Something wrong on this page? Report an error.