Code execution via omitted cProfile unsafe import
Published Jan 10, 2026 · Updated Jan 10, 2026
Static analysis bypass in Trail of Bits Fickling 0.1.6 and earlier allows attackers to trigger code execution via crafted pickle files. The UnsafeImports analysis omits cProfile from its unsafe-import blocklist, so cProfile.run carrying an attacker-supplied code string is rated SUSPICIOUS rather than OVERTLY_MALICIOUS. Execution occurs only when a workflow trusts that lower-severity verdict and then deserializes the pickle, granting the payload the workflow process's privileges.
Summary
What happened
Static analysis bypass in Trail of Bits Fickling 0.1.6 and earlier allows attackers to trigger code execution via crafted pickle files. The UnsafeImports analysis omits cProfile from its unsafe-import blocklist, so cProfile.run carrying an attacker-supplied code string is rated SUSPICIOUS rather than OVERTLY_MALICIOUS. Execution occurs only when a workflow trusts that lower-severity verdict and then deserializes the pickle, granting the payload the workflow process's privileges.
The record
- CVE
- CVE-2026-22607
- Published
- Jan 10, 2026
- Updated
- Jan 10, 2026
- Vendor
- Trail of Bits
- Product
- Fickling
- Classifications
- CWE-502, CWE-184, T1203
- 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?
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
- cProfile.run malicious-pickle 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