Arbitrary code execution via unsafe-import blocklist bypass
Published Dec 16, 2025 · Updated Dec 16, 2025
Static-analysis bypass in Trail of Bits Fickling before 0.1.6 allows attackers to trigger arbitrary code execution via a crafted pickle file. The unsafe_imports method omits marshal and types from its disallowed-module list, so calls through marshal.loads and types.FunctionType are rated likely safe. Execution requires a user or automated workflow to trust Fickling's result and then deserialize the attacker-controlled file; analysis alone does not run the payload.
Summary
What happened
Static-analysis bypass in Trail of Bits Fickling before 0.1.6 allows attackers to trigger arbitrary code execution via a crafted pickle file. The unsafe_imports method omits marshal and types from its disallowed-module list, so calls through marshal.loads and types.FunctionType are rated likely safe. Execution requires a user or automated workflow to trust Fickling's result and then deserialize the attacker-controlled file; analysis alone does not run the payload.
The record
- CVE
- CVE-2025-67747
- Published
- Dec 16, 2025
- Updated
- Dec 16, 2025
- Vendor
- Trail of Bits
- Product
- Fickling
- Classifications
- CWE-184, CWE-502, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 16, 2025CVE publishedPublication date reported by the CVE source.
- Dec 16, 2025Record 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.6
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
- GHSA-565g-hwwr-4pp3 crafted 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