NLTK versions before 3.10.3 fail to use validated absolute paths when invoking the Graphviz dot binary in dependencygraph.dot2img and AlignedSent._repr_svg_, allowing attackers to execute arbitrary code by placing a malicious dot binary in the search path or current working directory. Attackers can exploit bare-name binary resolution on Windows via the current working directory or on Unix-like systems via relative PATH entries to execute their binary instead of the legitimate Graphviz tool.
CVE-2026-78680
Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-25. a secondary CVSS source baseline 7.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.8
- EG Score
- 7.8(high)
- EG Risk
- 51(Track*)EG Risk 51/100SSVC: Track*
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity78% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- 0%
- EPSS %ILE
- 2%
- KEV
- Not listed
Published
August 25, 2026
Last Modified
August 25, 2026
Advisory Details (2)
Auto-updated Aug 25, 2026NLTK before 3.10.3 Arbitrary Code Execution via Graphviz dot Binary | Advisories | VulnCheck
https://www.vulncheck.com/advisories/nltk-before-arbitrary-code-execution-via-graphviz-dot-binaryUncontrolled search path when invoking the Graphviz 'dot' binary (CWE-426/CWE-427) · Advisory · nltk/nltk · GitHub
https://github.com/nltk/nltk/security/advisories/GHSA-6hwm-xvph-95vmVendor Advisories for CVE-2026-78680(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(4 across 4 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nltk | 3.10.0-1 ... 3.9.3-1 (9 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nltk | 3.10.0-1 ... 3.9.3-1 (6 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nltk | 3.10.0-1, 3.10.1-1, 3.9.1-2, 3.9.2-1, 3.9.3-1 | 3.10.3-1 | — |
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nltk | 0.8 ... 3.9b1 (68 versions) | 3.10.3 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 62× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-19 04:39 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-16 15:56 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 03:32 UTCEG score recompute
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-14 03:12 UTCEG score recompute
- 2026-09-13 02:56 UTCEG score recompute
- 2026-09-12 02:40 UTCEG score recompute
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 14:30 UTCEG score recompute
- 2026-09-10 14:14 UTCEG score recompute
- 2026-09-09 01:19 UTCEG score recompute
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-07 17:07 UTCEG score recompute
- 2026-09-06 16:52 UTCEG score recompute
- 2026-09-06 13:48 UTCEPSS rescore
- 2026-09-04 16:21 UTCEG score recompute
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-02 15:44 UTCEG score recompute
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 15:21 UTCEG score recompute
Show 37 moreShow fewer
- 2026-09-01 15:21 UTCGHSA enrichment
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-09-01 03:12 UTCGHSA enrichment
- 2026-08-31 15:04 UTCGHSA enrichment
- 2026-08-31 02:54 UTCEG score recompute
- 2026-08-31 02:54 UTCGHSA enrichment
- 2026-08-30 19:18 UTCEPSS rescore
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 14:46 UTCGHSA enrichment
- 2026-08-30 02:38 UTCEG score recompute
- 2026-08-30 02:38 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 14:30 UTCGHSA enrichment
- 2026-08-29 02:22 UTCEG score recompute
- 2026-08-29 02:21 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 14:10 UTCGHSA enrichment
- 2026-08-28 02:02 UTCEG score recompute
- 2026-08-28 02:01 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 13:53 UTCGHSA enrichment
- 2026-08-27 01:45 UTCEG score recompute
- 2026-08-27 01:45 UTCGHSA enrichment
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-26 13:38 UTCGHSA enrichment
- 2026-08-26 01:30 UTCEG score recompute
- 2026-08-26 01:30 UTCGHSA enrichment
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 13:22 UTCEG score recompute
- 2026-08-25 13:22 UTCGHSA enrichment
- 2026-08-25 12:53 UTCEG score recompute
- 2026-08-25 12:53 UTCGHSA enrichment
- 2026-08-25 02:19 UTCEG score recompute
- 2026-08-25 01:50 UTCEG score recompute
- 2026-08-25 01:50 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-78680?
When was CVE-2026-78680 disclosed?
Is CVE-2026-78680 actively exploited?
What is the CVSS score of CVE-2026-78680?
How do I remediate CVE-2026-78680?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-78680
Is Your Infrastructure Affected by CVE-2026-78680?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.