Metrics
Affected Vendors & Products
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-p523-jq9w-64x9 | Fickling Blocklist Bypass: cProfile.run() |
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:*:*:*:*:*:*:*:* | |
| Metrics |
cvssV3_1
|
Tue, 13 Jan 2026 22: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 cProfile module as unsafe. Because of this, a malicious pickle that uses cProfile.run() 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 Blocklist Bypass: cProfile.run() | |
| 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-13T21:49:38.169Z
Reserved: 2026-01-07T21:50:39.534Z
Link: CVE-2026-22607
Updated: 2026-01-13T21:49:27.585Z
Status : Analyzed
Published: 2026-01-10T02:15:49.780
Modified: 2026-01-16T18:58:22.570
Link: CVE-2026-22607
No data.
OpenCVE Enrichment
Updated: 2026-01-12T14:36:41Z
Github GHSA