Metrics
Affected Vendors & Products
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-wfq2-52f7-7qvj | Fickling has a bypass via runpy.run_path() and runpy.run_module() |
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Fri, 16 Jan 2026 19:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:trailofbits:fickling:*:*:*:*:*:python:*:* | |
| Metrics |
cvssV3_1
|
Tue, 13 Jan 2026 20:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Mon, 12 Jan 2026 14:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Trailofbits
Trailofbits fickling |
|
| Vendors & Products |
Trailofbits
Trailofbits fickling |
Sat, 10 Jan 2026 01:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Fickling has a bypass via runpy.run_path() and runpy.run_module() | |
| Weaknesses | CWE-184 CWE-502 |
|
| References |
| |
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-01-13T19:58:14.707Z
Reserved: 2026-01-07T21:50:39.533Z
Link: CVE-2026-22606
Updated: 2026-01-13T19:58:00.953Z
Status : Analyzed
Published: 2026-01-10T02:15:49.637
Modified: 2026-01-16T18:59:35.140
Link: CVE-2026-22606
No data.
OpenCVE Enrichment
Updated: 2026-01-12T14:36:55Z
Github GHSA