CVE-2026-0848

{"id": "CVE-2026-0848", "cveTags": [], "metrics": {"cvssMetricV30": [{"type": "Secondary", "source": "security@huntr.dev", "cvssData": {"scope": "CHANGED", "version": "3.0", "baseScore": 10.0, "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 6.0, "exploitabilityScore": 3.9}]}, "published": "2026-03-05T21:16:14.263", "references": [{"url": "https://huntr.com/bounties/08b109bb-ac24-403f-9422-1c246ce60202", "source": "security@huntr.dev"}, {"url": "https://huntr.com/bounties/08b109bb-ac24-403f-9422-1c246ce60202", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "security@huntr.dev", "description": [{"lang": "en", "value": "CWE-20"}]}], "descriptions": [{"lang": "en", "value": "NLTK versions <=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."}, {"lang": "es", "value": "Las versiones de NLTK &lt;=3.9.2 son vulnerables a ejecuci\u00f3n de c\u00f3digo arbitrario debido a una validaci\u00f3n de entrada inadecuada en el m\u00f3dulo StanfordSegmenter. El m\u00f3dulo carga din\u00e1micamente archivos .jar de Java externos sin verificaci\u00f3n ni sandboxing. Un atacante puede suministrar o reemplazar el archivo JAR, permitiendo la ejecuci\u00f3n de bytecode Java arbitrario en el momento de la importaci\u00f3n. Esta vulnerabilidad puede ser explotada a trav\u00e9s de m\u00e9todos como el envenenamiento de modelos, ataques MitM o el envenenamiento de dependencias, lo que lleva a ejecuci\u00f3n remota de c\u00f3digo. El problema surge de la ejecuci\u00f3n directa del archivo JAR a trav\u00e9s de un subproceso con entrada de classpath no validada, permitiendo que clases maliciosas se ejecuten cuando son cargadas por la JVM."}], "lastModified": "2026-03-09T13:36:08.413", "sourceIdentifier": "security@huntr.dev"}