Approved changes feed: RSS · Atom
cpe:2.3:a:trailofbits:fickling:*:*:*:*:*:python:*:*
part: a version: * update: *
| Vendor | Trailofbits (6524af29-571d-5cd0-b937-ac8aee3b3053) |
|---|---|
| Product | Fickling (5fe03817-c799-521d-9b4b-14c38c4110f9) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | python |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-22612 |
vulnerable | 2026-06-08 07:51:13.306902 |
Fickling vulnerable to detection bypass due to "builtins" blindness
Fickling is a Python pickling decompiler and static analyzer. Prior to version 0.1.7, Fickling is vulnerable to detection bypass due to "builtins" blindness. This issue has been patched in version 0.1.7.
Published: 2026-01-10T01:35:25.197Z
Updated: 2026-01-12T18:18:29.466Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-22609 |
vulnerable | 2026-06-08 07:51:13.286826 |
Fickling has Static Analysis Bypass via Incomplete Dangerous Module Blocklist
Fickling is a Python pickling decompiler and static analyzer. Prior to version 0.1.7, the unsafe_imports() method in Fickling's static analyzer fails to flag several high-risk Python modules that can be used for arbitrary code execution. Malicious pickles importing these modules will not be detected as unsafe, allowing attackers to bypass Fickling's primary static safety checks. This issue has been patched in version 0.1.7.
Published: 2026-01-10T01:35:18.152Z
Updated: 2026-01-14T19:51:31.740Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-22606 |
vulnerable | 2026-06-08 07:51:13.285522 |
Fickling has a bypass via runpy.run_path() and runpy.run_module()
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.
Published: 2026-01-10T01:35:00.797Z
Updated: 2026-01-13T19:58:14.707Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.