Security readout for executives and security teams
Plain-English summary
NLTK versions before 3.9.3 can extract downloaded language packages without first confirming their integrity. An attacker able to intercept network traffic or poison DNS could substitute malicious package contents, potentially compromising systems that download them. The risk is serious because no account or user interaction is required once the network position is established.
Executive priority
Treat this as an urgent supply-chain integrity issue. Prioritize internet-connected, production, development, and automated build systems that download NLTK data. Upgrade promptly and investigate untrusted historical downloads, while recognizing that the supplied sources do not establish active exploitation.
Technical view
CVE-2026-63310 is a CWE-494 flaw in the NLTK downloader. Before version 3.9.3, downloaded package files are not integrity-verified before extraction. The supplied CVSS 4.0 score is 9.3, reflecting network reachability, low attack complexity, and potentially high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely where NLTK earlier than 3.9.3 is installed and its downloader retrieves packages across a network susceptible to interception or DNS manipulation. Systems that never invoke the downloader may have lower practical exposure. The bundle provides no CPEs or deployment-specific evidence, so asset-level confirmation is required.
Exploitation context
The described attack requires control over package-download traffic through a man-in-the-middle position or DNS poisoning. The supplied record does not identify this CVE as being in KEV and provides no evidence of active exploitation. Exploit prevalence and observed targeting therefore remain unconfirmed.
Researcher notes
The failure occurs after download and before extraction, making archive contents the primary trust boundary. CVSS 4.0 is 9.3 with AV:N/AC:L/AT:N/PR:N/UI:N and high vulnerable-system impacts. No CPE identifiers or exploitation evidence are supplied. Validate the precise affected installation range and remediation behavior against the vendor advisory.
Mitigation direction
- Upgrade NLTK to version 3.9.3 or later, following the vendor advisory.
- Prioritize systems that dynamically download NLTK packages in production or privileged environments.
- Restrict package downloads to trusted networks and approved destinations until upgrades are complete.
- Rebuild or replace previously downloaded packages if their provenance cannot be established.
- Check vendor guidance for any additional integrity or cleanup recommendations.
Validation and detection
- Inventory installed NLTK versions and identify every instance earlier than 3.9.3.
- Determine which applications invoke the NLTK downloader and when downloads last occurred.
- Confirm remediated environments resolve NLTK to version 3.9.3 or later.
- Review relevant network, DNS, and download records for unexpected sources or redirections.
- Verify existing downloaded packages came from trusted sources; investigate uncertain provenance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-494: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-63310 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——VulnCheckCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:H1.65.5VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Base CVSS 3.1 score
7.1HighVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitHub Security Advisory (GHSA-5wp5-5229-5g6q)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: NLTK before 3.9.3 Missing Post-Download Integrity VerificationCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Download of Code Without Integrity Check
Download of Code Without Integrity Check represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.