CVE-2026-12252: In nltk/nltk versions 3.9.3 and earlier, five Stanford interface classes (StanfordPOSTagger, StanfordNERTagger

Q: How do I fix CVE-2026-12252?

nltk: upgrade to newer than 3.9.3. Exact commands for each OS are on this page.

Q: Is CVE-2026-12252 being exploited?

CVE-2026-12252 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-12252 affect?

CVE-2026-12252 affects nltk. Severity is high (CVSS 7.8). 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. Th

Q: How urgent is CVE-2026-12252?

Priority 35/100. High severity; Public exploit reference

Routine

HIGH 7.8UPGRADE

CVE-2026-12252 is a high-severity flaw (CVSS 7.8) affecting nltk. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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, wh

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	7.8 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.2% (top 91%)
CISA exploited list	No
Weakness	CWE-94
Published	2026-07-04
Last modified	2026-10-25

Publisher (CNA): huntr.dev · Vendor: nltk

Last updated 2026-10-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-07-04 02:16 UTCPublished CVE record published
2026-10-25 15:10 UTCUpdated Record last modified

nltk nltk UPGRADE

Affected: <= 3.9.3

Fixed in: newer than 3.9.3

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy nltk || rpm -q nltk || nltk --version

2. UPGRADE to newer than 3.9.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade nltk

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade nltk

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-12252?

nltk: upgrade to newer than 3.9.3. Exact commands for each OS are on this page.

Is CVE-2026-12252 being exploited?

CVE-2026-12252 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-12252 affect?

CVE-2026-12252 affects nltk. Severity is high (CVSS 7.8). 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. Th

How urgent is CVE-2026-12252?

Priority 35/100. High severity; Public exploit reference

Software pages

Java vulnerabilities

Related CVEs

CVE-2026-12259 MEDIUM 6.5 DOWNGRADE In nltk version 3.9.4, the `nltk.downloader.Downloader._download_package()` function writes downloaded package
CVE-2026-12261 MEDIUM 6.5 UPGRADE A vulnerability in `nltk.downloader` in nltk/nltk versions <= 3.9.4 allows for cross-package resource and mode
CVE-2026-12372 LOW 3.7 DOWNGRADE A Server-Side Request Forgery (SSRF) vulnerability exists in nltk/nltk versions 3.9.4 and the current develop

References

← Back to latest CVEs