Skip to main content
CVE-2026-22608VulnerabilityPublished Updated

CVE-2026-22608: trailofbits fickling · Incomplete List of Disallowed Inputs

Affects trailofbits ficklingSource CVE Database V5

0

Not known to be exploited · CVSS 8.9 High : upgrade to 0.1.7 soon.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score
8.9High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 33% 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:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
trailofbitsficklingAffected
  • <0.1.7
Fixed in
  • 0.1.7
PyPIficklingpkg:pypi/ficklingOther threatsAffected
  • <0.1.7
Fixed in
  • 0.1.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Upgrade fickling to version 0.1.7 or later immediately to ensure the patch blocking 'ctypes' and 'pydoc' modules is applied. 2. Supplement static analysis with dynamic runtime monitoring to detect suspicious deserialization activities or unexpected module usage, especially involving 'ctypes' or 'pydoc'. 3. Implement strict input validation and sanitization on all Python pickled data received from untrusted or external sources before analysis. 4. Employ network segmentation and least privilege principles to limit the impact of potential RCE on systems running fickling. 5. Regularly audit and review security tools and their update status within security operations to prevent use of outdated vulnerable versions. 6. Consider alternative or complementary pickle scanning tools that have robust blocking of dangerous modules and verify their detection capabilities against known evasion techniques. 7. Educate developers and security analysts about the risks of unsafe deserialization and the importance of using updated tools.

Description

Fickling is a Python pickling decompiler and static analyzer. Prior to version 0.1.7, both ctypes and pydoc modules aren't explicitly blocked. Even other existing pickle scanning tools (like picklescan) do not block pydoc.locate. Chaining these two together can achieve RCE while the scanner still reports the file as LIKELY_SAFE. This issue has been patched in version 0.1.7.

References

Community reviews

Loading reviews…