Security readout for executives and security teams
Plain-English summary
NLTK versions through 3.9.4 can execute malicious Python code when an application loads a specially crafted parser model. Successful exploitation could compromise data, alter systems, or disrupt services using the application’s privileges. Risk depends on whether untrusted parties can influence model files loaded by TransitionParser.
Executive priority
Treat internet-facing or multi-tenant applications loading externally influenced parser models as an immediate remediation priority. Upgrade promptly and constrain model provenance. For installations without TransitionParser usage or untrusted model ingestion, verify that conclusion and schedule the dependency update through normal urgent patching processes.
Technical view
TransitionParser.parse() deserializes model files using pickle_load() with restricted=False. WarningUnpickler does not restrict class resolution, allowing unsafe pickle objects to trigger arbitrary Python code. The vulnerable production path affects NLTK through 3.9.4 and is fixed in 3.10.0. Exploitation requires a crafted model file to be loaded.
Likely exposure
Highest exposure exists in applications using NLTK TransitionParser that accept, download, synchronize, or otherwise load model files from untrusted or weakly controlled sources. Merely having NLTK installed does not establish an exploitable path. Applications using unrelated NLTK functionality may not be directly exposed.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not listed as KEV in the bundle. Exploitation requires the target application to load an attacker-crafted model file. The reported CVSS score is 9.6 because successful exploitation can execute code with the application user’s privileges and affect downstream resources.
Researcher notes
The key weakness is CWE-502 unsafe deserialization. Although NLTK contains RestrictedUnpickler, the described production path instead uses WarningUnpickler, whose class resolution remains unrestricted. Exposure analysis should focus on model-file trust boundaries and application privileges. The supplied evidence does not identify public exploitation or quantify real-world vulnerable deployments.
Mitigation direction
- Upgrade affected NLTK installations to version 3.10.0 or later.
- Prevent applications from loading parser models supplied or modified by untrusted parties.
- Restrict model storage permissions and verify model provenance before use.
- Review the vendor advisory for any additional deployment-specific guidance.
Validation and detection
- Inventory deployed and bundled NLTK versions, including transitive dependencies.
- Identify applications calling TransitionParser.parse() and document every model-file source.
- Confirm whether external users or compromised pipelines can influence loaded model files.
- Verify production environments run NLTK 3.10.0 or later.
- Review relevant systems for unexpected activity associated with parser model loading.
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-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-78683 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.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
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:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H2.86VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.4CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Base CVSS 3.1 score
9.6CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/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-rhp5-r9x4-f5g2)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: NLTK before 3.10.0 Remote Code Execution via Unsafe Pickle DeserializationCVE 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.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.