CVE-2026-78682
SSRF in NLTK proxy handling allows internal access and malicious package install.
Is CVE-2026-78682 being exploited?
Not confirmed. CVE-2026-78682 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.25% probability of exploitation in the next 30 days.
How severe is CVE-2026-78682?
CVE-2026-78682 is rated High with a CVSS score of 8.7. 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-78682?
Yes. A fix has been recorded for CVE-2026-78682. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-78682 affect?
CVE-2026-78682 affects NLTK < 3.10.3, nltk.pathsec.urlopen, nltk.data.load, nltk.downloader.Downloader, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-78682?
Upgrade to NLTK >=3.10.3; restrict/validate HTTP proxy access and downloader sources.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Proxy-based SSRF exposes internal HTTP services, lets attackers load forged downloader indexes and install attacker-controlled packages (potential RCE/supply-chain compromise).
Immediate action required
- affected< 3.10.3
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.