CVE 8.9 HIGH

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

8.9 / 10
HIGH
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

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.

AI Analysis

A malicious pickle can be classified as SUSPICIOUS instead of OVERTLY_MALICIOUS due to Fickling not treating Python’s runpy module as unsafe, potentially leading to execution of attacker-controlled code.

Basic Information

ID CVE-2026-22606
Source GitHub_M
Published Jan 10, 2026 at 01:35

Affected Product

Vendor trailofbits
Product fickling
Version < 0.1.7
Affected Versions trailofbits fickling < 0.1.7

CWE Classification

AI Assessment

AI Score 8.9 / 10
AI Severity High
Vendor Trail of Bits
Product Fickling
Version < 0.1.7

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.