SSRF in Nltk
CVE-2026-63311
- CVSS v3
- 5.3 Medium
- Public exploits
- None known
- EPSS
- 0.003 · 27.5th percentile
- Published
- 2026-08-22
NLTK before 3.10.0 (affected versions <= 3.9.4) contains a server-side request forgery (SSRF) vulnerability in the validate_network_url() function in nltk/pathsec.py. The _resolve_hostname() helper catches OSError and ValueError during socket.getaddrinfo() and returns an empty list; when DNS resolution fails, the validation loop executes no IP checks and the function fails open, allowing urlopen() to proceed without validation. An attacker who can trigger DNS resolution failures or use DNS rebinding can bypass SSRF protections and reach restricted network resources, including cloud metadata endpoints (e.g., 169.254.169.254).
Vulnerability class: SSRF (Server-Side Request Forgery)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.3 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N.
- Attack Vector
- Network
AV:N - Attack Complexity
- Low
AC:L - Privileges Required
- None
PR:N - User Interaction
- None
UI:N - Scope
- Unchanged
S:U - Confidentiality
- None
C:N - Integrity
- Low
I:L - Availability
- None
A:N
EPSS exploit prediction
EPSS 0.003, 27.5th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
Weakness classification (CWE)
References
- GitHub Security Advisory (GHSA-3gqm-fcw5-w839) (vendor-advisory, Exploit, Mitigation, Vendor Advisory)
- VulnCheck Advisory: NLTK before 3.10.0 SSRF via DNS Resolution Failure (Third Party Advisory, third-party-advisory)