What’s Vulnerable › Vulnerabilities

CVE-2026-22606: Fickling has a bypass via runpy.run_path() and runpy.run_module()

• Severity: high (CVSS 7.8 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.5% probability of exploitation in the next 30 days
• Public exploit or detection template: yes
• Published: 2026-01-10 · updated 2026-06-17
• Weakness: CWE-184

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.

Affected products

• trailofbits fickling: before 0.1.7 — fixed in 0.1.7

How to fix

Upgrade to a fixed version: trailofbits fickling 0.1.7. Check the vendor advisory for mitigations.

References

• https://github.com/trailofbits/fickling/commit/9a2b3f89bd0598b528d62c10a64c1986fcb09f66
• https://github.com/trailofbits/fickling/releases/tag/v0.1.7
• https://github.com/trailofbits/fickling/security/advisories/GHSA-wfq2-52f7-7qvj
• https://github.com/trailofbits/fickling/security/advisories/GHSA-wfq2-52f7-7qvj

Get alerted when CVE-2026-22606 or the next vulnerability affects your stack