CVE-2026-22607: trailofbits fickling · Incomplete List of Disallowed Inputs
Affects trailofbits ficklingSource CVE Database V5
Not known to be exploited · CVSS 8.9 High : upgrade to 0.1.7 soon.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.1.7
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 10 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade trailofbits fickling to 0.1.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| trailofbitsfickling | Affected
| Fixed in
|
PyPIficklingpkg:pypi/ficklingOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
European organizations should immediately upgrade all instances of Fickling to version 0.1.7 or later, which correctly classifies cProfile usage as overtly malicious. Additionally, organizations should audit their workflows and products to identify any reliance on Fickling for pickle deserialization security gating. Where possible, avoid deserializing pickle data from untrusted or unauthenticated sources altogether. Implement defense-in-depth by combining static analysis tools like Fickling with runtime monitoring and sandboxing of deserialization processes. Educate developers and security teams about the risks of pickle deserialization and the limitations of static analyzers. Consider alternative serialization formats that are safer, such as JSON or protobuf, especially for external data exchange. Regularly review and update security tools to incorporate the latest threat intelligence and patches. Finally, monitor logs and network activity for anomalous behavior indicative of exploitation attempts involving pickle deserialization.
Description
Fickling is a Python pickling decompiler and static analyzer. Fickling versions up to and including 0.1.6 do not treat Python's cProfile module as unsafe. Because of this, a malicious pickle that uses cProfile.run() is classified as SUSPICIOUS instead of OVERTLY_MALICIOUS. If a user relies on Fickling's output to decide whether a pickle is safe to deserialize, this misclassification can lead them to execute attacker-controlled code on their system. This affects any workflow or product that uses Fickling as a security gate for pickle deserialization. This issue has been patched in version 0.1.7.