CVE catalog

CVE-2026-12252

Severity: High · CVSS 7.8CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Published: Jul 4, 2026, 12:58:58 AM UTC
Source: [NVD] · [CVE record]
EPSS: 0.19% · Oct 25, 2026

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.

Vulnerable and fixed packages

Distribution-reported package versions and fixes. These do not depend on matching against the OpenFactory package catalog.

Distribution	Package	Release	Version	Status
Debian	nltk	sid	`3.10.3-1`	fixed
Debian	nltk	forky	`3.10.3-1`	fixed
Debian	nltk	trixie	`3.9.1-2`	vulnerable
Debian	nltk	bookworm	`3.8-1`	vulnerable
Cpe	nltk	Not reported	Not reported	vulnerable
Cpe	nltk	Not reported	Not reported	unknown
Pip	nltk	Not reported	`3.9.4`	fixed
PyPI	nltk	Not reported	`0.8`	vulnerable
PyPI	nltk	Not reported	`0.9`	vulnerable
PyPI	nltk	Not reported	`0.9.3`	vulnerable
PyPI	nltk	Not reported	`0.9.4`	vulnerable
PyPI	nltk	Not reported	`0.9.5`	vulnerable
PyPI	nltk	Not reported	`0.9.6`	vulnerable
PyPI	nltk	Not reported	`0.9.7`	vulnerable
PyPI	nltk	Not reported	`0.9.8`	vulnerable
PyPI	nltk	Not reported	`0.9.9`	vulnerable
PyPI	nltk	Not reported	`2.0.1`	vulnerable
PyPI	nltk	Not reported	`2.0.1rc1`	vulnerable
PyPI	nltk	Not reported	`2.0.1rc2-git`	vulnerable
PyPI	nltk	Not reported	`2.0.1rc3`	vulnerable
PyPI	nltk	Not reported	`2.0.1rc4`	vulnerable
PyPI	nltk	Not reported	`2.0.2`	vulnerable
PyPI	nltk	Not reported	`2.0.3`	vulnerable
PyPI	nltk	Not reported	`2.0.4`	vulnerable
PyPI	nltk	Not reported	`2.0.5`	vulnerable
PyPI	nltk	Not reported	`2.0b4`	vulnerable
PyPI	nltk	Not reported	`2.0b5`	vulnerable
PyPI	nltk	Not reported	`2.0b6`	vulnerable
PyPI	nltk	Not reported	`2.0b7`	vulnerable
PyPI	nltk	Not reported	`2.0b8`	vulnerable
PyPI	nltk	Not reported	`2.0b9`	vulnerable
PyPI	nltk	Not reported	`3.0.0`	vulnerable
PyPI	nltk	Not reported	`3.0.0b1`	vulnerable
PyPI	nltk	Not reported	`3.0.0b2`	vulnerable
PyPI	nltk	Not reported	`3.0.1`	vulnerable
PyPI	nltk	Not reported	`3.0.2`	vulnerable
PyPI	nltk	Not reported	`3.0.3`	vulnerable
PyPI	nltk	Not reported	`3.0.4`	vulnerable
PyPI	nltk	Not reported	`3.0.5`	vulnerable
PyPI	nltk	Not reported	`3.1`	vulnerable
PyPI	nltk	Not reported	`3.2`	vulnerable
PyPI	nltk	Not reported	`3.2.1`	vulnerable
PyPI	nltk	Not reported	`3.2.2`	vulnerable
PyPI	nltk	Not reported	`3.2.3`	vulnerable
PyPI	nltk	Not reported	`3.2.4`	vulnerable
PyPI	nltk	Not reported	`3.2.5`	vulnerable
PyPI	nltk	Not reported	`3.3`	vulnerable
PyPI	nltk	Not reported	`3.4`	vulnerable
PyPI	nltk	Not reported	`3.4.1`	vulnerable
PyPI	nltk	Not reported	`3.4.2`	vulnerable
PyPI	nltk	Not reported	`3.4.3`	vulnerable
PyPI	nltk	Not reported	`3.4.4`	vulnerable
PyPI	nltk	Not reported	`3.4.5`	vulnerable
PyPI	nltk	Not reported	`3.5`	vulnerable
PyPI	nltk	Not reported	`3.5b1`	vulnerable
PyPI	nltk	Not reported	`3.6`	vulnerable
PyPI	nltk	Not reported	`3.6.1`	vulnerable
PyPI	nltk	Not reported	`3.6.2`	vulnerable
PyPI	nltk	Not reported	`3.6.3`	vulnerable
PyPI	nltk	Not reported	`3.6.4`	vulnerable
PyPI	nltk	Not reported	`3.6.5`	vulnerable
PyPI	nltk	Not reported	`3.6.6`	vulnerable
PyPI	nltk	Not reported	`3.6.7`	vulnerable
PyPI	nltk	Not reported	`3.7`	vulnerable
PyPI	nltk	Not reported	`3.8`	vulnerable
PyPI	nltk	Not reported	`3.8.1`	vulnerable
PyPI	nltk	Not reported	`3.9`	vulnerable
PyPI	nltk	Not reported	`3.9.1`	vulnerable
PyPI	nltk	Not reported	`3.9.2`	vulnerable
PyPI	nltk	Not reported	`3.9.3`	vulnerable
PyPI	nltk	Not reported	`3.9b1`	vulnerable
PyPI	nltk	Not reported	`3.9.4`	fixed
Opensuse	python-nltk	tumbleweed	`3.10.3-1.1`	fixed
Cpe	nltk	Not reported	Not reported	unknown

Fixed-version evidence

Distribution	Package	Type	Release	Fixed version	Urgency	Origin	Bugs
Debian	nltk	source	sid	`3.10.3-1`	not yet assigned	Not reported	[1143456]
Debian	nltk	source	forky	`3.10.3-1`	not yet assigned	Not reported	[1143456]
Debian	nltk	source	trixie	`(unfixed)`	not yet assigned	Not reported	[1143456]
Debian	nltk	source	bookworm	`(unfixed)`	not yet assigned	Not reported	[1143456]
Pip	nltk	pip	Not reported	`3.9.4`	Not reported	GHSA-9R6G-266R-89X4	Not reported
PyPI	nltk	PyPI	Not reported	`3.9.4`	Not reported	PYSEC-2026-2085	Not reported
Opensuse	python-nltk	rpm	tumbleweed	`3.10.3-1.1`	Not reported	OPENSUSE-SU-2026:11587-1	Not reported

[Debian bug #1143456]

Notes

[trixie] nltk: Minor issue [bookworm] nltk: Minor issue

OpenFactory catalog packages

[Debian 12 (Bookworm)]

[python3-nltk]Affected
Source package: [nltk]
Details (2)
- 3.8-1 · all · bookworm
  Affected
  nvd · nltk · debian · bookworm; nvd · nltk · debian · 12
- 3.8-1 · all · bookworm
  Affected
  nvd · nltk · debian · bookworm; nvd · nltk · debian · 12

[Debian 13 (Trixie)]

[python3-nltk]Affected
Source package: [nltk]
Details (2)
- 3.9.1-2 · all · trixie
  Affected
  nvd · nltk · debian · 13
- 3.9.1-2 · all · trixie
  Affected
  nvd · nltk · debian · 13

[openSUSE Tumbleweed]

[python313-nltk]Unknown
Source package: [python-nltk]
Details (1)
- 3.10.3-1.1 · noarch · tumbleweed
  Unknown · Fixed: 3.10.3-1.1
  Version impact unknown
  nvd · python-nltk · opensuse · tumbleweed
[python314-nltk]Unknown
Source package: [python-nltk]
Details (1)
- 3.10.3-1.1 · noarch · tumbleweed
  Unknown · Fixed: 3.10.3-1.1
  Version impact unknown
  nvd · python-nltk · opensuse · tumbleweed

Observed: Oct 25, 2026, 3:29:40 PM UTC

References

[Debian Security Tracker] · [FIRST EPSS] · [GitHub Advisory Database] · [National Vulnerability Database (NVD)] · [OSV Package Vulnerability Database] · [Red Hat security advisories and VEX] · [SUSE security advisories and VEX]