NLTK before 3.10.3 SSRF Protection Bypass via Proxy (CVE-2026-78682) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-78682

NLTK before 3.10.3 SSRF Protection Bypass via Proxy

Answer in brief

CVE-2026-78682 records a Unknown severity vulnerability in NLTK before 3.10.3 SSRF Protection Bypass via Proxy. The current sources do not mark it as known exploited. The current feed maps nltk/nltk (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 25, 2026Updated Aug 25, 2026Source checked Aug 25, 2026First seen by HOL Aug 25, 2026Material review Aug 25, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps nltk/nltk (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
nltk/nltkgeneric	>=0 <3.10.3	3.10.3

Recommended response

Check inventory. Check lockfiles and deployed manifests for nltk/nltk.
Review the reported fix. Update nltk/nltk to 3.10.3 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 25, 2026

Sources and claim methodology

Upstream source description

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.

Quoted source text, attributed separately from HOL analysis.