NLTK before 3.10.3 contains a remote code execution vulnerability in AllowlistUnpickler that validates only the pickle module string and not the… (CVE-2026-71513)
NLTK versions before 3.10.3 contain a remote code execution vulnerability in the AllowlistUnpickler component. The vulnerability arises because the AllowlistUnpickler validates only the pickle module string but not the global name, enabling attackers to resolve dotted names via attribute traversal to callables outside the allowlisted namespace. This allows crafted untrusted transition-parser models to execute arbitrary commands when loaded through allowlisted_pickle_load in TransitionParser.parse.
AI Analysis
Technical Summary
The vulnerability identified as CVE-2026-71513 affects NLTK versions prior to 3.10.3. It involves the AllowlistUnpickler class, which attempts to restrict unpickling to safe modules by validating the pickle module string but fails to validate the global name. This flaw permits attackers to exploit attribute traversal to invoke callables outside the intended allowlist, leading to remote code execution. Specifically, maliciously crafted transition-parser models can trigger arbitrary command execution during model loading via the allowlisted_pickle_load function in TransitionParser.parse.
Potential Impact
Successful exploitation allows remote attackers to execute arbitrary code on affected systems without privileges, potentially leading to full system compromise. The vulnerability impacts confidentiality, integrity, and availability, as indicated by the CVSS vector (C:H/I:H/A:H). There are no known exploits in the wild at this time.
Mitigation Recommendations
A fixed version, NLTK 3.10.3 or later, addresses this vulnerability. Users should upgrade to version 3.10.3 or newer to remediate the issue. Patch status is not explicitly confirmed in the provided data, but the version boundary implies the fix is included starting from 3.10.3. Until upgraded, avoid loading untrusted transition-parser models using allowlisted_pickle_load.
NLTK before 3.10.3 contains a remote code execution vulnerability in AllowlistUnpickler that validates only the pickle module string and not the… (CVE-2026-71513)
Description
NLTK versions before 3.10.3 contain a remote code execution vulnerability in the AllowlistUnpickler component. The vulnerability arises because the AllowlistUnpickler validates only the pickle module string but not the global name, enabling attackers to resolve dotted names via attribute traversal to callables outside the allowlisted namespace. This allows crafted untrusted transition-parser models to execute arbitrary commands when loaded through allowlisted_pickle_load in TransitionParser.parse.
CVSS v3.1
Score 8.8high
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
The vulnerability identified as CVE-2026-71513 affects NLTK versions prior to 3.10.3. It involves the AllowlistUnpickler class, which attempts to restrict unpickling to safe modules by validating the pickle module string but fails to validate the global name. This flaw permits attackers to exploit attribute traversal to invoke callables outside the intended allowlist, leading to remote code execution. Specifically, maliciously crafted transition-parser models can trigger arbitrary command execution during model loading via the allowlisted_pickle_load function in TransitionParser.parse.
Potential Impact
Successful exploitation allows remote attackers to execute arbitrary code on affected systems without privileges, potentially leading to full system compromise. The vulnerability impacts confidentiality, integrity, and availability, as indicated by the CVSS vector (C:H/I:H/A:H). There are no known exploits in the wild at this time.
Mitigation Recommendations
A fixed version, NLTK 3.10.3 or later, addresses this vulnerability. Users should upgrade to version 3.10.3 or newer to remediate the issue. Patch status is not explicitly confirmed in the provided data, but the version boundary implies the fix is included starting from 3.10.3. Until upgraded, avoid loading untrusted transition-parser models using allowlisted_pickle_load.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-5gh2-94qg-qppq
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-71513"]
- Ecosystems
- []
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a8a27f9acd9273b499bc9d0
Added to database: 08/22/2026, 22:51:37 UTC
Last enriched: 08/22/2026, 22:52:08 UTC
Last updated: 08/23/2026, 00:26:32 UTC
Views: 4
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.