PatchSiren

nltk CVE debriefs

These pages are published after PatchSiren validates generated defensive summaries against stored public CVE and source evidence.

MEDIUM nltk CVE published 2026-08-27

CVE-2026-81727

AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-08-27T17:21:03.533Z and has not been modified since then. This CVE record indicates a medium-severity vulnerability in NLTK versions before 3.10.3, allowing attackers to overwrite files outside the install root through pre-existing hardlinks. The vulnerability is exploitable by attackers with write acc [truncated]

HIGH nltk CVE published 2026-08-27

CVE-2026-81726

CVE-2026-81726 is a path traversal vulnerability in NLTK through 3.10.3 model-artifact APIs. This vulnerability allows attackers to bypass pathsec enforcement by using raw file operations on caller-controlled paths, potentially leading to unauthorized file read or write operations outside allowed sandbox roots. Developers and administrators should review and update NLTK versions, implement compensating co [truncated]

MEDIUM nltk CVE published 2026-08-27

CVE-2026-81725

The CVE-2026-81725 record indicates a regular expression denial of service vulnerability in NLTK's Pl196xCorpusReader. This vulnerability allows attackers to cause quadratic CPU consumption by supplying malformed TEI blocks with many unmatched opening tags, potentially leading to a denial of service through public APIs like words() and tagged_words(). The issue is resolved in NLTK version 3.10.3 or later. [truncated]

MEDIUM NLTK CVE published 2026-08-27

CVE-2026-81724

AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-08-27T17:21:03.100Z and has not been modified since then. The NVD entry is currently Analyzed. The vulnerability is caused by an uncontrolled recursion in nltk.featstruct.FeatStructReader, which allows unauthenticated attackers to cause a denial of service by supplying deeply nested feature-structure i [truncated]

MEDIUM nltk CVE published 2026-08-27

CVE-2026-81723

AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-08-27T17:21:02.957Z and has not been modified since then. NLTK versions before 3.10.3 contain a quadratic CPU exhaustion vulnerability in XMLCorpusView._read_xml_fragment() that rescans accumulated XML fragments on every 1 KiB block read. Attackers can provide malformed XML corpus files to cause severe [truncated]

HIGH nltk CVE published 2026-08-26

CVE-2026-80205

The CVE-2026-80205 vulnerability affects NLTK versions before 3.10.0, specifically in the Text.findall() and TokenSearcher.findall() methods. These methods accept user-supplied regular expressions without validation or timeout, allowing attackers to supply crafted regex patterns that cause catastrophic backtracking. This results in indefinite CPU saturation and denial of service to all users of the Python [truncated]

HIGH nltk CVE published 2026-08-25

CVE-2026-79676

AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-08-25T16:17:28.177Z and has not been modified since then. The NVD entry is currently Analyzed. Organizations using NLTK versions before 3.10.3 should be aware of the potential path traversal vulnerability and take steps to patch or mitigate the vulnerability. This includes reviewing and updating corpus [truncated]

CRITICAL nltk CVE published 2026-08-25

CVE-2026-79675

The NLTK library before version 3.10.3 contains a critical vulnerability (CVE-2026-79675) that allows attackers to inject malicious JVM flags through the per-call options parameter in the java() function. This can lead to arbitrary code execution, with a CVSS score of 9.3. The vulnerability is caused by inadequate validation of JVM options passed to the java() function, enabling attackers to supply danger [truncated]

HIGH nltk CVE published 2026-08-25

CVE-2026-79674

AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-08-25T16:17:27.873Z and has not been modified since then. The NVD entry is currently Analyzed. NLTK versions before 3.10.3 contain a path sandbox bypass vulnerability in corpus-reader constructors that allows attackers to read files outside the intended data root. Attackers can supply arbitrary corpus [truncated]

CRITICAL nltk CVE published 2026-08-25

CVE-2026-79657

The NLTK library versions before 3.10.3 contain a remote code execution vulnerability due to insecure pickle deserialization. This vulnerability is caused by allowlisted pickle loaders trusting entire module namespaces instead of specific safe callables, allowing attackers to craft malicious pickle payloads and execute arbitrary commands during model or tokenizer artifact loading. The vulnerability affect [truncated]

CRITICAL nltk CVE published 2026-08-25

CVE-2026-78683

AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-08-25T02:16:53.033Z and has not been modified since then. The NVD entry is currently Analyzed. The NLTK library before version 3.10.0 contains an unsafe pickle deserialization vulnerability in the TransitionParser.parse() method. This method calls pickle_load() with the default restricted=False, allowi [truncated]

HIGH nltk CVE published 2026-08-25

CVE-2026-78681

The CVE-2026-78681 vulnerability affects NLTK versions before 3.10.3, which use xml.etree.ElementTree to parse XML in multiple modules. This allows entity declarations in document DTDs to be honored, enabling attackers to craft XML payloads with nested entity declarations. These payloads can expand from hundreds of bytes to megabytes in memory, causing denial of service. Users of affected NLTK versions sh [truncated]

HIGH nltk CVE published 2026-08-25

CVE-2026-78680

CVE-2026-78680 is a high-severity vulnerability in NLTK versions before 3.10.3. The vulnerability allows attackers to execute arbitrary code by manipulating the search path or current working directory to invoke a malicious Graphviz dot binary instead of the legitimate one. This issue arises from NLTK's failure to use validated absolute paths when invoking the Graphviz dot binary in dependencygraph.dot2im [truncated]

HIGH nltk CVE published 2026-08-22

CVE-2026-70626

AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-08-22T15:16:21.100Z and has not been modified since then. NLTK versions before 3.9.4 contain a symlink escape vulnerability in CorpusReader.open() that allows local attackers to read arbitrary files outside the corpus root due to inadequate path validation. This vulnerability exists because path valida [truncated]

HIGH nltk CVE published 2026-08-22

CVE-2026-65915

AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-08-22T15:16:19.500Z and has not been modified since then. The vulnerability affects NLTK versions before 3.10.0, which contain a logic bug in FileSystemPathPointer.open() that makes the sandbox validation check permanently inert. This allows attackers to pass file:// URLs to nltk.data.load() to read ar [truncated]

HIGH nltk CVE published 2026-08-22

CVE-2026-63312

AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-08-22T15:16:19.367Z and has not been modified since then. CVE-2026-63312 is a HIGH-rated vulnerability in NLTK's StreamBackedCorpusView before version 3.10.0. Attackers can read arbitrary local files by bypassing pathsec.ENFORCE via direct calls to builtins.open(), controlling the fileid argument. This [truncated]

HIGH nltk CVE published 2026-08-22

CVE-2026-62384

AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-08-22T15:16:18.700Z and has not been modified since then. This vulnerability affects NLTK versions before 3.10.2, specifically in the FramenetCorpusReader, allowing for a symlink-based sandbox bypass. This could enable attackers to read arbitrary XML files outside the corpus root. Organizations should [truncated]

LOW nltk CVE published 2026-08-22

CVE-2026-71514

AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-08-22T14:16:33.560Z and has not been modified since then. The CrubadanCorpusReader in NLTK 3.9.4 through 3.10.2 contains a path traversal vulnerability. The _load_lang_ngrams function joins the corpus root with crubadan_code, read from the corpus table.txt mapping file, and opens the result using the b [truncated]

HIGH nltk CVE published 2026-08-22

CVE-2026-71513

CVE-2026-71513 is a remote code execution vulnerability in NLTK's AllowlistUnpickler. The vulnerability validates only the pickle module string and not the global name, allowing attackers to resolve dotted names by attribute traversal to callables outside the allowlisted namespace. This could lead to arbitrary command execution when TransitionParser.parse loads the model through allowlisted_pickle_load. D [truncated]

HIGH nltk CVE published 2026-08-20

CVE-2026-72818

AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-08-20T22:18:05.087Z and has not been modified since then. The NVD entry is currently Received. Services that use the nltk library's TweetTokenizer, especially those handling untrusted social-media text, should prioritize patching to prevent potential high-impact attacks. This includes any service that [truncated]

LOW nltk CVE published 2026-08-09

CVE-2026-12372

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` [truncated]

MEDIUM nltk CVE published 2026-08-03

CVE-2026-12259

The CVE record for CVE-2026-12259 was published on 2026-08-03T08:17:17.880Z and has not been modified since then. The NVD entry is currently Received. This vulnerability affects nltk version 3.9.4, allowing attackers to tamper with package responses, potentially leading to malicious package installation. The vulnerability can be exploited through a compromised mirror, malicious proxy, or other source-subs [truncated]

HIGH nltk CVE published 2026-07-04

CVE-2026-12252

CVE-2026-12252 is a high-severity vulnerability (CVSS Score: 7.8) affecting nltk/nltk versions 3.9.3 and earlier. The vulnerability exists in five Stanford interface classes: StanfordPOSTagger, StanfordNERTagger, StanfordParser, StanfordDependencyParser, and StanfordNeuralDependencyParser. These classes accept user-controllable JAR paths and execute them via the `java()` function, which invokes `subproces [truncated]

HIGH nltk CVE published 2026-06-22

CVE-2026-54293

The NLTK library's path traversal vulnerability allows for arbitrary file reads, impacting NLP systems and Python developers using NLTK. Defenders should verify NLTK version 3.10.0-rc1 or later, adjust access controls, and monitor for anomalous filesystem access patterns. The vulnerability is fixed in version 3.10.0-rc1. This CVE record was published on 2026-06-22T19:17:20.983Z and has not been modified s [truncated]

HIGH nltk CVE published 2026-06-17

CVE-2026-12199

A vulnerability in `nltk.app.wordnet_app` up to version 3.9.3 allows unauthenticated remote shutdown of the local WordNet Browser HTTP server when started in its default mode. The server listens on all interfaces and processes a specific unauthenticated GET request to terminate the process immediately via `os._exit(0)`. This results in a denial of service, impacting service availability. The issue arises [truncated]

HIGH nltk CVE published 2026-03-20

CVE-2026-33236

CVE-2026-33236 is a high-severity vulnerability in the Natural Language Toolkit (NLTK) that allows attackers to perform path traversal attacks. The vulnerability exists in versions 3.9.3 and prior, where the NLTK downloader fails to validate the `subdir` and `id` attributes when processing remote XML index files. This allows attackers to control a remote XML index server and provide malicious values conta [truncated]

HIGH nltk CVE published 2026-03-20

CVE-2026-33231

CVE-2026-33231 is a high-severity vulnerability in the Natural Language Toolkit (NLTK) that allows unauthenticated remote shutdown of the local WordNet Browser HTTP server. The vulnerability affects NLTK versions 3.9.3 and prior. A simple GET request can cause the process to terminate immediately, resulting in a denial of service. The issue was patched in commit bbaae83db86a0f49e00f5b0db44a7254c268de9b.

HIGH nltk CVE published 2026-03-09

CVE-2026-0846

CVE-2026-0846 is a high-severity vulnerability in the NLTK library's `filestring()` function, which allows for arbitrary file reads due to improper validation of input paths. The function directly opens files specified by user input without sanitization, enabling attackers to access sensitive system files by providing absolute paths or traversal paths. This vulnerability can be exploited locally or remote [truncated]

HIGH nltk CVE published 2026-03-04

CVE-2026-0847

CVE-2026-0847 is a high-severity vulnerability in the Natural Language Toolkit (NLTK) library, affecting versions up to and including 3.9.2. The vulnerability is caused by multiple CorpusReader classes, including WordListCorpusReader, TaggedCorpusReader, and BracketParseCorpusReader, failing to properly sanitize or validate file paths. This allows attackers to traverse directories and access sensitive fil [truncated]

HIGH nltk CVE published 2026-02-18

CVE-2025-14009

A critical vulnerability exists in the NLTK downloader component of nltk/nltk, affecting all versions. The _unzip_iter function in nltk/downloader.py uses zipfile.extractall() without performing path validation or security checks. This allows attackers to craft malicious zip packages that, when downloaded and extracted by NLTK, can execute arbitrary code. The vulnerability arises because NLTK assumes all [truncated]