Skip to main content
VulnerabilityPublished Updated

CVE-2026-22606: 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, 09:16 UTC

CVSS 4.0 base score
8.9High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 41% 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 26 Oct 2026.

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

European organizations should immediately upgrade Fickling to version 0.1.7 or later, which patches the vulnerability by correctly classifying runpy usage as overtly malicious. Until upgrade is possible, organizations should implement additional manual or automated checks for pickle data that invoke runpy or similar dynamic execution modules. Avoid deserializing pickle data from untrusted or unauthenticated sources altogether. Employ defense-in-depth by isolating pickle deserialization processes in sandboxed or containerized environments with minimal privileges. Monitor logs and alerts for suspicious pickle deserialization activities, especially those involving runpy or unexpected module executions. Incorporate alternative safer serialization formats (e.g., JSON, protobuf) where feasible. Conduct security awareness training for developers and security teams about the risks of pickle deserialization and the limitations of current detection tools. Finally, review and update incident response plans to address potential exploitation scenarios involving malicious pickle payloads.

Description

Fickling is a Python pickling decompiler and static analyzer. Fickling versions up to and including 0.1.6 do not treat Python’s runpy module as unsafe. Because of this, a malicious pickle that uses runpy.run_path() or runpy.run_module() 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.

References

Community reviews

Loading reviews…