CVE-2026-22612: trailofbits fickling · Deserialization of Untrusted Data
Affects trailofbits ficklingSource CVE Database V5
Public exploit available · CVSS 8.9 High : upgrade to 0.1.7 as a priority.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 24% 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: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
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
- Immediately upgrade all instances of Fickling to version 0.1.7 or later to apply the patch that fixes the detection bypass.
- Conduct a thorough audit of all deserialization processes within your environment, especially those involving Python pickle data, to identify and remediate any similar weaknesses.
- Implement strict input validation and sanitization for any data deserialized by internal tools or applications to prevent untrusted data from being processed.
- Employ runtime monitoring and anomaly detection to identify unusual behaviors indicative of deserialization attacks.
- Restrict network access to systems running Fickling or related analysis tools to trusted users and networks only.
- Educate development and security teams about the risks of unsafe deserialization and the importance of using secure coding practices.
- Review and update incident response plans to include scenarios involving deserialization vulnerabilities.
- Consider using alternative or additional static analysis tools that have robust protections against deserialization bypasses as a defense-in-depth measure.
Description
Fickling is a Python pickling decompiler and static analyzer. Prior to version 0.1.7, Fickling is vulnerable to detection bypass due to "builtins" blindness. This issue has been patched in version 0.1.7.