{"answers":{"affected":"3 open source packages ship an affected version, including nltk. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-12252 exists.","fix":"Upgrade nltk to 3.9.4 or later.","what":"CVE-2026-12252 is a high-severity code injection vulnerability in nltk/nltk, published on 4 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-12252 and fix it if it is affected.\n\nWhat it is: CVE-2026-12252 is a high-severity code injection vulnerability in nltk/nltk, published on 4 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-12252 exists.\n\nAffected packages and fixed versions:\n- nltk (PyPI): affected all versions; fixed in 3.9.4\n- nltk (PyPI): affected all versions; fixed in 3.9.4\n- nltk (PyPI): affected all versions; fixed in 3.9.4\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-12252/ (Markdown: https://insights.sbomify.com/CVE-2026-12252/index.md)","id":"CVE-2026-12252","markdown":"https://insights.sbomify.com/CVE-2026-12252/index.md","name":"CVE-2026-12252","record":{"aliases":["DEBIAN-CVE-2026-12252","ECHO-aca5-37c5-5309","GHSA-9r6g-266r-89x4","MINI-j5j2-v7mg-2rqv","PYSEC-2026-2085","UBUNTU-CVE-2026-12252"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Python NLP library","requires_auth":"none","summary":"Attackers can execute arbitrary code by providing malicious JAR files to Stanford interface classes in the NLTK library due to missing integrity checks.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"nltk","vendor":"nltk"}],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"In nltk/nltk versions 3.9.3 and earlier, five Stanford interface classes (StanfordPOSTagger, StanfordNERTagger, StanfordParser, StanfordDependencyParser, and StanfordNeuralDependencyParser) are vulnerable to untrusted JAR code execution. These classes accept user-controllable JAR paths and execute them via the `java()` function, which invokes `subprocess.Popen()` without integrity verification. This vulnerability is identical to CVE-2026-0848, which was fixed for StanfordSegmenter by adding SHA256 verification. However, the fix was not applied to these additional classes, leaving them susceptible to arbitrary code execution when loading untrusted JAR files.","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":"Untrusted JAR Code Execution in Multiple Stanford Interface Classes in nltk/nltk","id":"CVE-2026-12252","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"Netskope Client Captive Portal WebView Persistence allowing SWG bypass issue","id":"CVE-2026-12254"},"packages":[{"ecosystem":"PyPI","fixed":["3.9.4"],"introduced":["0"],"last_affected":[],"package":"nltk","purl":null,"source":"GHSA-9r6g-266r-89x4"},{"ecosystem":"PyPI","fixed":["3.9.4"],"introduced":["0"],"last_affected":[],"package":"nltk","purl":"pkg:pypi/nltk","source":"GHSA-9r6g-266r-89x4"},{"ecosystem":"PyPI","fixed":["3.9.4"],"introduced":["0"],"last_affected":[],"package":"nltk","purl":"pkg:pypi/nltk","source":"PYSEC-2026-2085"}],"prev":{"headline":"Ultimate Member \u003c 2.12.1 - Unauthenticated Privilege Escalation via Role Selection Field","id":"CVE-2026-12251"},"products":["nltk/nltk"],"published":"2026-07-04","related":[{"cvss_score":10,"headline":"Arbitrary Code Execution in NLTK StanfordSegmenter via Untrusted JAR Loading","id":"CVE-2026-0848","kev_date_added":null,"published":"2026-03-05"},{"cvss_score":10,"headline":"Zip Slip Vulnerability in nltk/nltk Leading to Remote Code Execution","id":"CVE-2025-14009","kev_date_added":null,"published":"2026-02-18"},{"cvss_score":9.4,"headline":"NLTK before 3.10.0 Remote Code Execution via Unsafe Pickle Deserialization","id":"CVE-2026-78683","kev_date_added":null,"published":"2026-08-25"},{"cvss_score":9.3,"headline":"NLTK before 3.10.3 Remote Code Execution via Unsafe Pickle Deserialization","id":"CVE-2026-79657","kev_date_added":null,"published":"2026-08-25"},{"cvss_score":9.3,"headline":"NLTK before 3.10.3 JVM Argument Injection via Per-Call Options","id":"CVE-2026-79675","kev_date_added":null,"published":"2026-08-25"},{"cvss_score":8.8,"headline":"NLTK 3.10.2 Path Traversal via corpus-reader constructors","id":"CVE-2026-79674","kev_date_added":null,"published":"2026-08-25"},{"cvss_score":8.7,"headline":"nltk PorterStemmer before 3.10.3 Quadratic-time DoS","id":"CVE-2026-81722","kev_date_added":null,"published":"2026-08-27"}],"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":"US public information, NVD API terms","name":"NVD"},{"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-07-06","vendors":["nltk"]},"summary":"Attackers can execute arbitrary code by providing malicious JAR files to Stanford interface classes in the NLTK library due to missing integrity checks.","url":"https://insights.sbomify.com/CVE-2026-12252/"}