CVE-2026-12372: CWE-918 Server-Side Request Forgery (SSRF) in nltk nltk/nltk
CVE-2026-12372 is a Server-Side Request Forgery (SSRF) vulnerability in the nltk library affecting version 3.9.4 and the current develop branch. The issue arises because the function intended to block internal network addresses does not reject IPs in the RFC 6598 shared address space (100.64.0.0/10). This allows an attacker controlling a URL input to cause the application to send requests to shared-address-space hosts, potentially exposing internal infrastructure. The vulnerability impacts confidentiality only and does not allow code execution or availability disruption.
AI Analysis
Technical Summary
The vulnerability exists in nltk's `nltk.pathsec.validate_network_url()` function, which attempts to prevent SSRF by rejecting internal IP addresses. However, it fails to reject IPs in the RFC 6598 shared address space (100.64.0.0/10) because Python's `ipaddress` module does not classify these addresses as private or global, and the validation logic only checks for `is_private` and a few explicit categories. Consequently, an attacker able to influence URLs passed to NLTK's network-loading helpers can exploit this to make the application send requests to hosts in the shared address space, potentially exposing non-public infrastructure reachable from the application host. No code execution or integrity/availability impact is claimed.
Potential Impact
The impact is limited to confidentiality exposure via SSRF. An attacker may cause the application to send unauthorized requests to internal or shared address space hosts, potentially revealing sensitive information about internal infrastructure. There is no indication of code execution, data modification, or denial of service.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, users should avoid passing untrusted URLs to the affected `validate_network_url()` function or network-loading helpers in nltk. Additional network-level controls or application-layer filtering may help mitigate risk.
CVE-2026-12372: CWE-918 Server-Side Request Forgery (SSRF) in nltk nltk/nltk
Description
CVE-2026-12372 is a Server-Side Request Forgery (SSRF) vulnerability in the nltk library affecting version 3.9.4 and the current develop branch. The issue arises because the function intended to block internal network addresses does not reject IPs in the RFC 6598 shared address space (100.64.0.0/10). This allows an attacker controlling a URL input to cause the application to send requests to shared-address-space hosts, potentially exposing internal infrastructure. The vulnerability impacts confidentiality only and does not allow code execution or availability disruption.
CVSS v3.0
Score 3.7low
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability exists in nltk's `nltk.pathsec.validate_network_url()` function, which attempts to prevent SSRF by rejecting internal IP addresses. However, it fails to reject IPs in the RFC 6598 shared address space (100.64.0.0/10) because Python's `ipaddress` module does not classify these addresses as private or global, and the validation logic only checks for `is_private` and a few explicit categories. Consequently, an attacker able to influence URLs passed to NLTK's network-loading helpers can exploit this to make the application send requests to hosts in the shared address space, potentially exposing non-public infrastructure reachable from the application host. No code execution or integrity/availability impact is claimed.
Potential Impact
The impact is limited to confidentiality exposure via SSRF. An attacker may cause the application to send unauthorized requests to internal or shared address space hosts, potentially revealing sensitive information about internal infrastructure. There is no indication of code execution, data modification, or denial of service.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, users should avoid passing untrusted URLs to the affected `validate_network_url()` function or network-loading helpers in nltk. Additional network-level controls or application-layer filtering may help mitigate risk.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- @huntr_ai
- Date Reserved
- 2026-06-16T06:05:39.765Z
- Cvss Version
- 3.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a7905b9bf8831d539631c3c
Added to database: 08/09/2026, 22:56:57 UTC
Last enriched: 08/09/2026, 23:15:00 UTC
Last updated: 08/09/2026, 23:16:20 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.