CVE-2026-22609: 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 26 Oct 2026, 06:26 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 49% 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-26.
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
1. Immediately upgrade Fickling to version 0.1.7 or later, where the unsafe_imports() method correctly detects all high-risk modules. 2. Implement strict validation and sandboxing of pickle files before analysis, including running Fickling in isolated environments to contain potential code execution. 3. Supplement static analysis with dynamic monitoring to detect suspicious behavior during pickle processing. 4. Restrict network access and permissions for systems running Fickling to minimize impact if exploited. 5. Educate developers and analysts about the risks of deserializing untrusted pickle data and encourage the use of safer serialization formats where possible. 6. Integrate vulnerability scanning and dependency checks into development pipelines to detect outdated versions of Fickling. 7. Monitor security advisories for any emerging exploits related to this CVE and apply patches promptly.
Description
Fickling is a Python pickling decompiler and static analyzer. Prior to version 0.1.7, the unsafe_imports() method in Fickling's static analyzer fails to flag several high-risk Python modules that can be used for arbitrary code execution. Malicious pickles importing these modules will not be detected as unsafe, allowing attackers to bypass Fickling's primary static safety checks. This issue has been patched in version 0.1.7.
References
- github.com/trailofbits/fickling/security/advisories/GHSA-q5qq-mvfm-j35x (opens in a new tab)
- github.com/trailofbits/fickling/commit/29d5545e74b07766892c1f0461b801afccee4f91 (opens in a new tab)
- github.com/trailofbits/fickling/commit/9a2b3f89bd0598b528d62c10a64c1986fcb09f66 (opens in a new tab)
- github.com/trailofbits/fickling/commit/b793563e60a5e039c5837b09d7f4f6b92e6040d1 (opens in a new tab)
- github.com/trailofbits/fickling/commit/eb299b453342f1931c787bcb3bc33f3a03a173f9 (opens in a new tab)
- github.com/trailofbits/fickling/releases/tag/v0.1.7 (opens in a new tab)