{"answers":{"affected":"1 open source package 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-0848 exists.","fix":"Upgrade nltk to 3.9.3 or later.","what":"CVE-2026-0848 is a critical code injection vulnerability in nltk/nltk, published on 5 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-0848 and fix it if it is affected.\n\nWhat it is: CVE-2026-0848 is a critical code injection vulnerability in nltk/nltk, published on 5 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-0848 exists.\n\nAffected packages and fixed versions:\n- nltk (PyPI): affected all versions; fixed in 3.9.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-0848/ (Markdown: https://insights.sbomify.com/CVE-2026-0848/index.md)","id":"CVE-2026-0848","markdown":"https://insights.sbomify.com/CVE-2026-0848/index.md","name":"CVE-2026-0848","record":{"aliases":["DEBIAN-CVE-2026-0848","GHSA-v2w2-xcg6-53wj","PYSEC-2026-99"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Python NLP library","requires_auth":"none","summary":"Attackers can execute arbitrary code by supplying malicious JAR files to the NLTK StanfordSegmenter module, affecting Python NLP applications.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"nltk","vendor":"nltk"}],"cvss":{"score":10,"severity":"critical","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"NLTK versions \u003c=3.9.2 are vulnerable to arbitrary code execution due to improper input validation in the StanfordSegmenter module. The module dynamically loads external Java .jar files without verification or sandboxing. An attacker can supply or replace the JAR file, enabling the execution of arbitrary Java bytecode at import time. This vulnerability can be exploited through methods such as model poisoning, MITM attacks, or dependency poisoning, leading to remote code execution. The issue arises from the direct execution of the JAR file via subprocess with unvalidated classpath input, allowing malicious classes to execute when loaded by the JVM.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":"2026-03-29","github_poc":3,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-03-29T08:20:30Z","kind":"github_poc","ref":"https://github.com/HyperPS/CVE-2026-0848","stars":0,"title":"nltk.tokenize.StanfordSegmenter dynamically loads external Java .jar files without verification or sandboxing. If an attacker can supply or replace the JAR (e.g., a poisoned model download, MITM package swap, or dependency poisoning), arbitrary Java bytecode executes at import time."},{"date":"2026-03-31T14:34:02Z","kind":"github_poc","ref":"https://github.com/fevar54/CVE-2026-0848-PoC-Improper-Input-Validation","stars":0,"title":"PoC de CVE-2026-0848: validacion de entrada indebida en NLTK que permite ejecucion de codigo via StanfordSegmenter."},{"date":"2026-03-31T15:12:27Z","kind":"github_poc","ref":"https://github.com/fevar54/CVE-2026-0848-Scanner---Herramienta-de-Detecci-n","stars":0,"title":"Scanner de CVE-2026-0848: detecta instalaciones de NLTK 3.9.2 o inferiores vulnerables. Reportes JSON/HTML/CSV."}],"tier":"weaponised"},"has_fix":true,"headline":"Arbitrary Code Execution in NLTK StanfordSegmenter via Untrusted JAR Loading","id":"CVE-2026-0848","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":1,"n_references":1,"next":{"headline":"crypto: ATAES132A response length allows stack buffer overflow","id":"CVE-2026-0849"},"packages":[{"ecosystem":"PyPI","fixed":["3.9.3"],"introduced":["0"],"last_affected":[],"package":"nltk","purl":"pkg:pypi/nltk","source":"PYSEC-2026-99"}],"prev":{"headline":"Path Traversal in nltk/nltk","id":"CVE-2026-0847"},"products":["nltk/nltk"],"published":"2026-03-05","related":[{"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":"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-03-06","vendors":["nltk"]},"summary":"Attackers can execute arbitrary code by supplying malicious JAR files to the NLTK StanfordSegmenter module, affecting Python NLP applications.","url":"https://insights.sbomify.com/CVE-2026-0848/"}