Server-Side Request Forgery (SSRF) Affecting nltk package, versions *


Severity

Recommended
low

Based on Debian security rating.

Threat Intelligence

EPSS
0.25% (17th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-DEBIAN13-NLTK-19256968
  • published25 Aug 2026
  • disclosed25 Aug 2026

Introduced: 25 Aug 2026

NewCVE-2026-78682  (opens in a new tab)
CWE-918  (opens in a new tab)

How to fix?

There is no fixed version for Debian:13 nltk.

NVD Description

Note: Versions mentioned in the description apply only to the upstream nltk package and not the nltk package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1