SSRF via fail-open DNS resolution
Published Aug 22, 2026 · Updated Aug 22, 2026
SSRF in NLTK before 3.10.0 allows remote attackers to reach restricted network resources when hostname resolution fails. In nltk/pathsec.py, _resolve_hostname() converts socket.getaddrinfo() errors into an empty list, so validate_network_url() performs no address checks and urlopen() proceeds. Reachability requires an application to pass attacker-controlled URLs into NLTK and a transient or attacker-induced DNS failure; successful requests can access internal services or cloud metadata.
Summary
What happened
SSRF in NLTK before 3.10.0 allows remote attackers to reach restricted network resources when hostname resolution fails. In nltk/pathsec.py, _resolve_hostname() converts socket.getaddrinfo() errors into an empty list, so validate_network_url() performs no address checks and urlopen() proceeds. Reachability requires an application to pass attacker-controlled URLs into NLTK and a transient or attacker-induced DNS failure; successful requests can access internal services or cloud metadata.
The record
- CVE
- CVE-2026-63311
- Published
- Aug 22, 2026
- Updated
- Aug 22, 2026
- Vendor
- NLTK Project
- Product
- NLTK
- Classifications
- CWE-918
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 22, 2026CVE publishedPublication date reported by the CVE source.
- Aug 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.10.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream DNS-resolution failure PoCproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo