Code execution via untrusted pickle deserialization
Published Apr 6, 2026 · Updated Apr 6, 2026
Code execution in pytries datrie 0.8.0 through 0.8.3 allows attackers to run Python code by loading a crafted trie file. Trie.load, Trie.read, and Trie.setstate pass the pickle data appended after a valid trie structure directly to pickle.load without restricting reconstructed objects. Exploitation requires an application or user to load the attacker-supplied file, after which the payload executes with the affected Python process's privileges.
Summary
What happened
Code execution in pytries datrie 0.8.0 through 0.8.3 allows attackers to run Python code by loading a crafted trie file. Trie.load, Trie.read, and Trie.setstate pass the pickle data appended after a valid trie structure directly to pickle.load without restricting reconstructed objects. Exploitation requires an application or user to load the attacker-supplied file, after which the payload executes with the affected Python process's privileges.
The record
- CVE
- CVE-2026-5659
- Published
- Apr 6, 2026
- Updated
- Apr 6, 2026
- Vendor
- pytries
- Product
- datrie
- Classifications
- CWE-502, CWE-20, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 6, 2026CVE publishedPublication date reported by the CVE source.
- Apr 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.8.0
- Affected versionversion=0.8.1
- Affected versionversion=0.8.2
- Affected versionversion=0.8.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Crafted trie pickle payload proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo