{"answers":{"affected":"3 open source packages ship an affected version, including nltk.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-78680 exists.","fix":"Upgrade nltk to 3.10.3 or later.","what":"CVE-2026-78680 is a high-severity command injection vulnerability in nltk, published on 25 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-78680 and fix it if it is affected.\n\nWhat it is: CVE-2026-78680 is a high-severity command injection vulnerability in nltk, published on 25 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-78680 exists.\n\nAffected packages and fixed versions:\n- nltk (PyPI): affected all versions; fixed in 3.10.3\n- nltk (PyPI): affected all versions; fixed in 3.10.3\n- nltk (PyPI): affected all versions; fixed in 3.10.3\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-78680/ (Markdown: https://insights.sbomify.com/CVE-2026-78680/index.md)","id":"CVE-2026-78680","markdown":"https://insights.sbomify.com/CVE-2026-78680/index.md","name":"CVE-2026-78680","record":{"aliases":["DEBIAN-CVE-2026-78680","ECHO-54ff-3814-cf1f","GHSA-6hwm-xvph-95vm","MINI-2v44-pxwv-4639","PYSEC-2026-3868"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Python NLP library","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary code by placing a malicious Graphviz binary in the search path, affecting NLTK users.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-426","name":"Untrusted Search Path"}],"description":"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"NLTK before 3.10.3 Arbitrary Code Execution via Graphviz dot Binary","id":"CVE-2026-78680","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"command_injection","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"NLTK before 3.10.3 Entity Expansion DoS via ElementTree","id":"CVE-2026-78681"},"packages":[{"ecosystem":"PyPI","fixed":["3.10.3"],"introduced":["0"],"last_affected":[],"package":"nltk","purl":null,"source":"GHSA-6hwm-xvph-95vm"},{"ecosystem":"PyPI","fixed":["3.10.3"],"introduced":["0"],"last_affected":[],"package":"nltk","purl":"pkg:pypi/nltk","source":"GHSA-6hwm-xvph-95vm"},{"ecosystem":"PyPI","fixed":["3.10.3"],"introduced":["0"],"last_affected":[],"package":"nltk","purl":"pkg:pypi/nltk","source":"PYSEC-2026-3868"}],"prev":{"headline":"GitPython before 3.1.59 Arbitrary File Read via TagReference.create","id":"CVE-2026-78679"},"products":["nltk"],"published":"2026-08-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-25","vendors":["nltk"]},"summary":"Attackers can execute arbitrary code by placing a malicious Graphviz binary in the search path, affecting NLTK users.","url":"https://insights.sbomify.com/CVE-2026-78680/"}