CVE-2026-12372lowCWE-918

CVE-2026-12372: low-severity vulnerability in nltk/nltk

Server-Side Request Forgery (SSRF) in nltk/nltk

Published · Updated

Follow this CVE+ Monitor nltk/nltk+ Monitor nltk

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

8Vexday Risk Score

No sign of exploitation. No public exploitation artifact known so far.

ssvc Trackcvss 3.7epss 0.3%
A Server-Side Request Forgery (SSRF) vulnerability exists in nltk/nltk versions 3.9.4 and the current develop branch. The `nltk.pathsec.validate_network_url()` function, intended to prevent SSRF by rejecting internal network addresses, fails to reject IPs in the RFC 6598 shared address space (`100.64.0.0/10`). This occurs because Python's `ipaddress` module does not classify such addresses as `is_private` or `is_global`, and the current guard only checks `is_private` and a few explicit categories. An attacker who can influence a URL passed to NLTK's network-loading helpers can exploit this vulnerability to make a strict-mode application send requests to shared-address-space hosts, potentially exposing non-public infrastructure reachable from the application host. The impact is limited to SSRF-style confidentiality exposure, with no code execution claimed.
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
Affected products
nltk · nltk/nltk
Related CVEs — nltk/nltk

In the same product, most dangerous first.

CVE-2021-3828HIGHInefficient Regular Expression Complexity in nltk/nltkEPSS 1.6%CVE-2021-3842HIGHInefficient Regular Expression Complexity in nltk/nltkEPSS 1.6%CVE-2025-14009HIGHZip Slip Vulnerability in nltk/nltk Leading to Remote Code ExecutionEPSS 1.0%CVE-2026-0847HIGHPath Traversal in nltk/nltkEPSS 1.0%CVE-2026-0848CRITICALArbitrary Code Execution in NLTK StanfordSegmenter via Untrusted JAR LoadingEPSS 0.8%CVE-2026-0846HIGHArbitrary File Read via Absolute Path Input in nltk.util.filestring()EPSS 0.6%