Safety: NLTK dot2img runs Graphviz 'dot' without the trusted-exec chokepoint, enabling local code execution via a
Affects safetySource GCVE Database
Not known to be exploited · CVSS 7.8 High : upgrade to 3.8.1_3 soon.
Data as of 17 Nov 2026, 19:33 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 7.8 |
|---|
- Patch
- Available – fixed in 3.8.1_3
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 13 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 16 Nov 2026.
What to do
Upgrade safety to 3.8.1_3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewsafetypkg:brew/safetyOther threats | 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 patch is available in NLTK version 3.8.1_3 that fixes this vulnerability by applying the trusted-execution checks to dot2img. Users should upgrade to version 3.8.1_3 or later to remediate this issue. Until patched, avoid running NLTK dot2img or rendering DependencyGraph visualizations on systems where untrusted users have write access to directories on your PATH. There are no vendor advisories stating no action is required or that the issue is already mitigated.
Description
The NLTK library's dot2img function executes the Graphviz 'dot' binary without applying the trusted-execution security checks that NLTK uses elsewhere. This allows a local unprivileged attacker on a POSIX system to place a malicious 'dot' executable in a writable directory on the victim's PATH, leading to arbitrary code execution when dot2img is invoked. The vulnerability arises because dot2img only performs a basic binary search without ownership or environment scrubbing, unlike other NLTK wrappers. This flaw enables local code execution in the victim's user context without requiring control over NLTK inputs.
References
- github.com/nltk/nltk/security/advisories/GHSA-7mxv-7h3q-9324 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-128134 (opens in a new tab)
- github.com/nltk/nltk/pull/3887 (opens in a new tab)
- github.com/nltk/nltk/commit/b002a7288c22db86fd6ca2d9526e3f91d6fda797 (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)