<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>NLTK (&lt; 3.9.3) - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/nltk--3.9.3/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Sat, 22 Aug 2026 15:31:26 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/nltk--3.9.3/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>NLTK Downloader Module Integrity Vulnerability</title><link>https://feed.craftedsignal.io/briefs/2026-08-nltk-integrity-vulnerability/</link><pubDate>Sat, 22 Aug 2026 15:31:26 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-08-nltk-integrity-vulnerability/</guid><description>NLTK versions prior to 3.9.3 fail to verify package integrity after download, allowing remote attackers to perform MitM or DNS poisoning attacks to inject and execute arbitrary code.</description><content:encoded><![CDATA[<p>NLTK (Natural Language Toolkit) versions before 3.9.3 contain a security flaw (CVE-2026-63310) in the downloader module. The library fails to perform integrity checks on packages after they are downloaded and before they are extracted. This vulnerability exposes users to potential remote code execution if an attacker can position themselves to intercept network traffic. By leveraging techniques such as man-in-the-middle (MitM) positioning or DNS poisoning, an attacker can substitute legitimate NLTK model packages with malicious archives. Because the library lacks validation of these downloaded files, it will proceed to extract and process the contents, potentially leading to the execution of attacker-supplied code on the host machine. This affects all users running vulnerable versions of NLTK across Windows, Linux, and macOS.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker performs reconnaissance to identify users or automated systems initiating NLTK package downloads.</li>
<li>Attacker establishes a MitM position on the network or poisons local DNS records to intercept requests to NLTK package servers.</li>
<li>Attacker intercepts the HTTP/HTTPS request initiated by the NLTK downloader module.</li>
<li>Attacker forces the NLTK client to download a spoofed, malicious package file.</li>
<li>NLTK downloader module completes the file transfer.</li>
<li>NLTK automatically proceeds to extract the malicious package contents without verifying cryptographic signatures or file hashes.</li>
<li>Extracted malicious payloads are executed by the NLTK library or the parent application process.</li>
<li>Attacker achieves arbitrary code execution on the target host.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this vulnerability allows for arbitrary code execution in the context of the user or process running the NLTK library. Given the widespread use of NLTK in data science, machine learning, and natural language processing pipelines, this could result in unauthorized data access, system compromise, and lateral movement within the affected environment.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Update the NLTK library to version 3.9.3 or later across all development and production environments.</li>
<li>Audit network traffic for unauthorized redirection or interception, specifically targeting traffic destined for NLTK package repositories.</li>
<li>Implement TLS interception or inspection where possible to identify malicious payload delivery during the download phase.</li>
<li>Monitor for unexpected process spawns from the parent application process responsible for NLTK package management.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>cve-2026-63312</category><category>path-traversal</category><category>library-vulnerability</category><category>python</category></item></channel></rss>