CVE-2026-63311
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:L
Summary
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).
Affected Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| nltk | nltk | 0 < 3.10.0 | affected |
| nltk | nltk | 3.10.0 | unaffected |
Weaknesses
- CWE-918: Server-Side Request Forgery (SSRF)
References
- https://github.com/nltk/nltk/security/advisories/GHSA-3gqm-fcw5-w839
- https://www.vulncheck.com/advisories/nltk-before-ssrf-via-dns-resolution-failure
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.