In Trail of Bits fickling through 0.1.12, the _process_import() method in fickle.py adds an imported name to the
Affects ficklingSource GCVE Database
Mentioned vulnerabilities
Not known to be exploited · CVSS 8.8 High : upgrade to 0.1.13 soon.
Data as of 31 Oct 2026, 01:38 UTC
Thin evidence
One scorer or none| CNA (BombadilSystems) | CVSS 3.1 | 8.8 |
|---|
- Affects
- Bits fickling through 0.1.12
- Patch
- Available – fixed in 0.1.13
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 30 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade fickling to 0.1.13.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
PyPIficklingpkg:pypi/ficklingOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
As of 2026-10-30, the vendor has added the demonstrated unsafe modules to the UNSAFE_IMPORTS denylist on the master branch, pending release. Released versions through 0.1.12 remain vulnerable. Users should upgrade to a fixed version once released. Until then, avoid using fickling.load() as a security gate for untrusted pickle data.
Description
Trail of Bits fickling versions through 0.1.12 contain a vulnerability in the _process_import() method that trusts imported names from standard library modules without verifying their behavior. This leads to the OvertlyBadEvals analysis pass skipping dangerous calls, allowing arbitrary code execution or file writes via trusted but unsafe callables. Demonstrated exploits include arbitrary code execution through dataclasses._create_fn and mailcap.findmatch, and arbitrary file writes via readline methods. The vulnerability is due to trusting module origin for callable safety and is distinct from a related CVE-2026-118938. The issue remains in released versions through 0.1.12, with a pending fix on the vendor master branch.