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).
References
| Link | Resource |
|---|---|
| https://github.com/nltk/nltk/security/advisories/GHSA-3gqm-fcw5-w839 | Exploit Mitigation Vendor Advisory |
| https://www.vulncheck.com/advisories/nltk-before-ssrf-via-dns-resolution-failure | Third Party Advisory |
Configurations
History
No history.
Information
Published : 2026-08-22 15:16
Updated : 2026-08-27 19:42
NVD link : CVE-2026-63311
Mitre link : CVE-2026-63311
CVE.ORG link : CVE-2026-63311
JSON object : View
Products Affected
nltk
- nltk
CWE
CWE-918
Server-Side Request Forgery (SSRF)
