CVE-2026-12252Patch(nltk / nltk)

LOWCVSS 7.8 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Patch nltk nltk systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD description

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.

0.5/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-94

Priority

LOW

Exploitation

NONE

PoC

YES

Patch

AVAILABLE

Momentum

NONE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • nltk

Threat summary

  • Patch or workaround signal is available
  • 1 mentions across 1 observed day

What's happening

  • Patch or workaround mentioned in 1 signal
  • Technical details provided in 1 signal
  • 1 total mentions across 1 day

Affected systems

Vendors
Products
nltk

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-07-04: 1Patch / Workaround · 2026-07-04: 1Technical Details · 2026-07-04: 107-04
Signal classification1 categories
Patch
1100.0%
Full discourse1 post
  • Upwind Security MDR@UpwindMDR
    Patch

    🚨High - NLTK Untrusted JAR Code Execution in Stanford Interfaces (CVE-2026-12252) Five of NLTK's Stanford wrapper classes - StanfordPOSTagger, StanfordNERTagger, StanfordParser, StanfordDependencyParser, and StanfordNeuralDependencyParser - accept user-controllable JAR paths and execute them via java() / subprocess.Popen() with no integrity verification. Loading an attacker-supplied or tampered JAR through any of these classes yields arbitrary code execution. It's the same flaw as CVE-2026-0848 (fixed for StanfordSegmenter with SHA256 verification), but that fix was never applied to these five classes. 👉Affected: nltk <= 3.9.3 - avoid loading untrusted JAR paths via the Stanford interfaces; apply the patched release once available.

    Post summary

    The tweet details a code execution vulnerability in Stanford interface wrappers and urges users to avoid untrusted JARs and apply the forthcoming patch.

    0000091
    236 followersView on X
CPE platform detail1 entries

1 of 1 entries

PartVendorProductVersionTarget SWTarget HW
Appnltknltk---

Explore more