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.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - 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. (CVE-2026-12252)

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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. (CVE-2026-12252)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	Name	Product	Family	Type	Severity
472275	Echo: nltk: security update to 3.9.4	Tenable Cloud Security	Echo Local Security Checks	Local	high
472275	Echo: nltk: security update to 3.9.4	Tenable Self-Hosted Container Security	Echo Local Security Checks	Local	high
471277	SCA: security update for nltk (GHSA-9r6g-266r-89x4)	Tenable Cloud Security	SCA Checks	Local	high
471277	SCA: security update for nltk (GHSA-9r6g-266r-89x4)	Tenable Self-Hosted Container Security	SCA Checks	Local	high
325348	Linux Distros Unpatched Vulnerability : CVE-2026-12252	Nessus	Misc.	Local	high

Detections

Analytics

CVE-2026-12252

high

Tenable Plugins

high

high

high

high

high