CVE-2026-0848
RCE in NLTK StanfordSegmenter via unverified JARs
Is CVE-2026-0848 being exploited?
Not confirmed. CVE-2026-0848 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.81% probability of exploitation in the next 30 days.
How severe is CVE-2026-0848?
CVE-2026-0848 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-0848?
Yes. A fix has been recorded for CVE-2026-0848. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-0848 affect?
CVE-2026-0848 affects NLTK <=3.9.2, StanfordSegmenter module, Python NLP workflows using NLTK. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-0848?
Upgrade NLTK to patched version; validate/sandbox external JARs
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution by loading unverified external JARs; attacker can run arbitrary Java bytecode on host
Patch when possible
- affected<= latest
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.