NLTK before 3.9.3 fails to verify file integrity after downloading packages and before extraction in the downloader module. (CVE-2026-63310)
NLTK versions prior to 3.9.3 contain a vulnerability in the downloader module where file integrity is not verified after downloading packages and before extraction. This flaw allows attackers to conduct man-in-the-middle or DNS poisoning attacks to inject malicious package contents that are extracted without validation. The vulnerability is tracked as CVE-2026-63310 and has a CVSS score of 7.1, indicating a high severity risk.
AI Analysis
Technical Summary
NLTK before version 3.9.3 fails to verify the integrity of downloaded packages in its downloader module before extracting them. This lack of verification enables attackers to exploit man-in-the-middle or DNS poisoning techniques to inject malicious content into the packages. The vulnerability is identified as CVE-2026-63310 and is associated with CWE-494 (Download of Code Without Integrity Check). The CVSS v3.1 base score is 7.1, reflecting network attack vector, high impact on integrity and availability, and requiring user interaction with high attack complexity and no privileges required.
Potential Impact
An attacker capable of intercepting or redirecting network traffic can inject malicious package contents into the NLTK downloader process. Because the downloader does not verify file integrity before extraction, these malicious contents can be executed or used by the application, potentially leading to code execution or denial of service. The confidentiality impact is low, but integrity and availability impacts are high.
Mitigation Recommendations
No official patch or fix is currently documented in the provided data. Users should upgrade to NLTK version 3.9.3 or later once available to ensure file integrity verification is performed. Until then, avoid using the downloader module in untrusted or insecure network environments. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
NLTK before 3.9.3 fails to verify file integrity after downloading packages and before extraction in the downloader module. (CVE-2026-63310)
Description
NLTK versions prior to 3.9.3 contain a vulnerability in the downloader module where file integrity is not verified after downloading packages and before extraction. This flaw allows attackers to conduct man-in-the-middle or DNS poisoning attacks to inject malicious package contents that are extracted without validation. The vulnerability is tracked as CVE-2026-63310 and has a CVSS score of 7.1, indicating a high severity risk.
CVSS v3.1
Score 7.1high
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
NLTK before version 3.9.3 fails to verify the integrity of downloaded packages in its downloader module before extracting them. This lack of verification enables attackers to exploit man-in-the-middle or DNS poisoning techniques to inject malicious content into the packages. The vulnerability is identified as CVE-2026-63310 and is associated with CWE-494 (Download of Code Without Integrity Check). The CVSS v3.1 base score is 7.1, reflecting network attack vector, high impact on integrity and availability, and requiring user interaction with high attack complexity and no privileges required.
Potential Impact
An attacker capable of intercepting or redirecting network traffic can inject malicious package contents into the NLTK downloader process. Because the downloader does not verify file integrity before extraction, these malicious contents can be executed or used by the application, potentially leading to code execution or denial of service. The confidentiality impact is low, but integrity and availability impacts are high.
Mitigation Recommendations
No official patch or fix is currently documented in the provided data. Users should upgrade to NLTK version 3.9.3 or later once available to ensure file integrity verification is performed. Until then, avoid using the downloader module in untrusted or insecure network environments. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-gf32-cmjh-8m9v
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-63310"]
- Ecosystems
- []
- Database Specific Severity
- CRITICAL
- Cvss Version
- 3.1
Threat ID: 6a8a27f7acd9273b499bc992
Added to database: 08/22/2026, 22:51:35 UTC
Last enriched: 08/22/2026, 22:52:27 UTC
Last updated: 08/23/2026, 01:45:46 UTC
Views: 5
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.