A Server-Side Request Forgery (SSRF) vulnerability exists in nltk/nltk versions 3.9.4 and the current develop branch. (CVE-2026-12372)
A Server-Side Request Forgery (SSRF) vulnerability exists in nltk version 3.9.4 and the current develop branch. The vulnerability arises because the function intended to block internal network addresses does not properly reject IPs in the RFC 6598 shared address space (100.64.0.0/10). This allows an attacker who can control a URL passed to NLTK's network-loading helpers to cause the application to send requests to shared-address-space hosts, potentially exposing internal infrastructure. The impact is limited to confidentiality exposure via SSRF, with no code execution or integrity impact reported.
AI Analysis
Technical Summary
The SSRF vulnerability in nltk (CVE-2026-12372) is due to the `nltk.pathsec.validate_network_url()` function failing to reject IP addresses in the RFC 6598 shared address space (100.64.0.0/10). This occurs because Python's `ipaddress` module does not classify these addresses as private or global, and the validation only checks for private IPs and some 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 internal shared-address-space hosts, potentially exposing non-public infrastructure accessible from the host. The vulnerability affects nltk version 3.9.4 and the current develop branch. The CVSS 3.0 base score is 3.7, indicating low severity, with impact limited to confidentiality loss. There is no known code execution or availability impact. No patch or official fix information is provided in the data.
Potential Impact
The vulnerability allows an attacker to perform SSRF attacks that can expose internal or shared-address-space infrastructure reachable from the application host. The impact is limited to confidentiality exposure; there is no indication of code execution, integrity, or availability impact. The CVSS score of 3.7 reflects a low severity confidentiality impact with high attack complexity and no privileges required.
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 NLTK's network-loading helpers or implement additional validation to block RFC 6598 shared address space IPs. Monitor vendor channels for updates or official patches addressing this SSRF vulnerability.
A Server-Side Request Forgery (SSRF) vulnerability exists in nltk/nltk versions 3.9.4 and the current develop branch. (CVE-2026-12372)
Description
A Server-Side Request Forgery (SSRF) vulnerability exists in nltk version 3.9.4 and the current develop branch. The vulnerability arises because the function intended to block internal network addresses does not properly reject IPs in the RFC 6598 shared address space (100.64.0.0/10). This allows an attacker who can control a URL passed to NLTK's network-loading helpers to cause the application to send requests to shared-address-space hosts, potentially exposing internal infrastructure. The impact is limited to confidentiality exposure via SSRF, with no code execution or integrity impact reported.
CVSS v3.0
Score 3.7low
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The SSRF vulnerability in nltk (CVE-2026-12372) is due to the `nltk.pathsec.validate_network_url()` function failing to reject IP addresses in the RFC 6598 shared address space (100.64.0.0/10). This occurs because Python's `ipaddress` module does not classify these addresses as private or global, and the validation only checks for private IPs and some 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 internal shared-address-space hosts, potentially exposing non-public infrastructure accessible from the host. The vulnerability affects nltk version 3.9.4 and the current develop branch. The CVSS 3.0 base score is 3.7, indicating low severity, with impact limited to confidentiality loss. There is no known code execution or availability impact. No patch or official fix information is provided in the data.
Potential Impact
The vulnerability allows an attacker to perform SSRF attacks that can expose internal or shared-address-space infrastructure reachable from the application host. The impact is limited to confidentiality exposure; there is no indication of code execution, integrity, or availability impact. The CVSS score of 3.7 reflects a low severity confidentiality impact with high attack complexity and no privileges required.
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 NLTK's network-loading helpers or implement additional validation to block RFC 6598 shared address space IPs. Monitor vendor channels for updates or official patches addressing this SSRF vulnerability.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-2jhm-w3mp-jcwr
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-12372"]
- Ecosystems
- []
- Database Specific Severity
- LOW
- Cvss Version
- 3.0
Threat ID: 6a79f0f4bf8831d539f646e1
Added to database: 08/10/2026, 15:40:36 UTC
Last enriched: 08/10/2026, 16:10:25 UTC
Last updated: 08/11/2026, 03:41:00 UTC
Views: 8
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.
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.