CVE-2026-0846
Arbitrary file read via nltk.filestring() due to unvalidated input paths.
Is CVE-2026-0846 being exploited?
Not confirmed. CVE-2026-0846 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.43% probability of exploitation in the next 30 days.
How severe is CVE-2026-0846?
CVE-2026-0846 is rated High with a CVSS score of 8.6. 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-0846?
Yes. A fix has been recorded for CVE-2026-0846. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-0846 affect?
CVE-2026-0846 affects nltk 3.9.2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-0846?
Upgrade to fixed nltk version when available; validate inputs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local/remote arbitrary file read; attacker can access sensitive files via user-supplied paths (e.g., web APIs).
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.