Loading vulnerability…
NLTK versions before 3.10.0, including versions through 3.9.4, contain an unsafe deserialization vulnerability in TransitionParser.parse(). The method invokes pickle loading with restricted deserialization disabled, causing use of WarningUnpickler. Because this unpickler does not restrict class resolution via find_class(), a malicious pickle model can invoke attacker-selected classes or functions through pickle gadget chains. NLTK includes RestrictedUnpickler, but the affected production deserialization path does not use it.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An unsafe Python pickle deserialization remote-code-execution vulnerability in NLTK's TransitionParser and related parsing call sites. An attacker able to supply or place a malicious model pickle can execute code with the privileges of the NLTK-dependent application when it loads the model.
A critical unsafe pickle deserialization vulnerability in NLTK TransitionParser.parse() that enables arbitrary code execution via crafted model files.
An unsafe pickle deserialization vulnerability in NLTK TransitionParser.parse() that can lead to arbitrary Python code execution when a crafted model file is loaded.
A network-accessible vulnerability affecting Debian Linux 11.0, 12.0, and 13.0. The supplied CVSS vectors indicate low attack complexity, no required privileges, and user interaction, with high potential impact to confidentiality, integrity, and availability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.