Code execution via incomplete runpy import blocklist
Published Jan 10, 2026 · Updated Jan 10, 2026
Safety-check bypass in Trail of Bits Fickling before 0.1.7 allows attackers to execute code via a crafted pickle file. The UnsafeImports analysis omits runpy from its unsafe-import blocklist, so runpy.run_path() and runpy.run_module() receive only a SUSPICIOUS rating. Code executes after a user or automated workflow accepts the scan result and deserializes the attacker-supplied pickle, granting the pickle the loader process's access.
Summary
What happened
Safety-check bypass in Trail of Bits Fickling before 0.1.7 allows attackers to execute code via a crafted pickle file. The UnsafeImports analysis omits runpy from its unsafe-import blocklist, so runpy.run_path() and runpy.run_module() receive only a SUSPICIOUS rating. Code executes after a user or automated workflow accepts the scan result and deserializes the attacker-supplied pickle, granting the pickle the loader process's access.
The record
- CVE
- CVE-2026-22606
- Published
- Jan 10, 2026
- Updated
- Jan 10, 2026
- Vendor
- Trail of Bits
- Product
- Fickling
- Classifications
- CWE-184, CWE-502, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 10, 2026CVE publishedPublication date reported by the CVE source.
- Jan 10, 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.1.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- runpy.run_path pickle safety-check bypass 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