cve.bz

CVE-2026-78682 nltk nltk: SSRF

8.7 highExploit referenceEPSS 0.4%Fix available

High (8.7) in nltk nltk. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in nltk 3.10.3.

On this page
NLTK before 3.10.3 contains a server-side request forgery vulnerability in nltk.pathsec.urlopen (and callers nltk.data.load, nltk.downloader.Downloader.index/download) when an HTTP proxy is configured. pathsec.urlopen validates the requested hostname locally, but proxy-handler inheritance disables the safe HTTP/HTTPS handlers so the actual fetch is performed by the proxy against a destination that is never re-validated. An attacker can supply a validated public URL that the proxy forwards to an internal loopback-only service, allowing disclosure of internal HTTP resources, loading of forged downloader indexes, and installation of attacker-chosen package content.

Severity

CVSS 4.0

8.7 high
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 38th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-08-25. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-78682 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-78682?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-78682?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-78682 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
nltkbefore 3.10.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-6ww7-3frv-cqxhPyPInltk<3.10.33.10.3
PYSEC-2026-3733PyPInltk<3.10.33.10.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13nltkno fix listedDEBIAN-CVE-2026-78682
Debian14nltk3.10.3-1DEBIAN-CVE-2026-78682

From the distributions' data via OSV.dev: the Debian Security Tracker. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This is a server-side request forgery (SSRF) vulnerability in NLTK when an HTTP proxy is configured. The flaw allows an attacker to bypass local hostname validation, enabling the proxy to forward requests to internal loopback services. This can lead to the disclosure of internal HTTP resources or the installation of attacker-controlled package content in Red Hat products utilizing NLTK with an HTTP proxy.

Red Hat's mitigation

To mitigate this issue, avoid configuring an HTTP proxy for NLTK if it is not strictly necessary. If an HTTP proxy must be used, implement strict network egress filtering to prevent NLTK from initiating connections to internal or loopback network addresses. This measure restricts the potential for an attacker to exploit the SSRF to access internal resources.

ProductPackageStateAdvisory
Red Hat OpenShift AI 2.25rhoai/odh-llama-stack-core-rhel9:1791873747Fixed 2026-10-21RHSA-2026:87410
Red Hat OpenShift AI 2.25rhoai/odh-pipeline-runtime-pytorch-llmcompressor-cuda-py312-rhel9:1791867208Fixed 2026-10-21RHSA-2026:87410
Red Hat OpenShift AI 2.25rhoai/odh-ta-lmes-job-rhel9:1791553527Fixed 2026-10-21RHSA-2026:87410
Red Hat OpenShift AI 2.25rhoai/odh-workbench-jupyter-pytorch-llmcompressor-cuda-py312-rhel9:1791867189Fixed 2026-10-21RHSA-2026:87410
Red Hat OpenShift AI 3.3rhoai/odh-llama-stack-core-rhel9:1789121286Fixed 2026-09-30RHSA-2026:73987
Red Hat OpenShift AI 3.4rhoai/odh-ta-lmes-job-rhel9:1791470318Fixed 2026-10-19RHSA-2026:84734
Red Hat OpenShift AI 3.4rhoai/odh-trustyai-garak-lls-provider-dsp-rhel9:1791785804Fixed 2026-10-19RHSA-2026:84734
Red Hat OpenShift AI 3.4rhoai/odh-trustyai-nemo-guardrails-server-rhel9:1791556128Fixed 2026-10-19RHSA-2026:84734
Red Hat OpenShift AI 3.5rhoai/odh-ogx-core-rhel9:1790963109Fixed 2026-10-21RHSA-2026:86891
Red Hat OpenShift AI 3.5rhoai/odh-ta-lmes-job-rhel9:1792501995Fixed 2026-10-21RHSA-2026:86891
Red Hat OpenShift AI 3.5rhoai/odh-trustyai-garak-lls-provider-dsp-rhel9:1791953275Fixed 2026-10-21RHSA-2026:86891
Exploit Intelligenceexploit-intelligence-tech-preview/vulnerability-analysis-rhel9Will not fix
Lightspeed Corelightspeed-core/lightspeed-stack-rhel9Affected
Lightspeed Corelightspeed-core/rag-tool-cpu-rhel9Affected
Lightspeed Corelightspeed-core/rag-tool-cuda-12.9-rhel9Affected
OpenShift Lightspeedopenshift-lightspeed/lightspeed-ocp-rag-rhel9Affected
OpenShift Lightspeedopenshift-lightspeed/lightspeed-service-api-rhel9Affected
OpenShift Lightspeedopenshift-lightspeed-tech-preview/lightspeed-rag-tool-rhel9Affected
OpenShift Lightspeedopenshift-lightspeed/lightspeed-service-api-rhel9Not affected
Red Hat Ansible Automation Platform 2ansible-automation-platform-25/lightspeed-chatbot-rhel8Will not fix
1 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-78682.

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON