CVE-2026-16760
Fickling check_safety() bypass: likely_safe_imports grants module-origin trust to unvalidated standard library callables
- High 8.8
Description
In Trail of Bits fickling through 0.1.12, the _process_import() method in fickle.py adds an imported name to the likely_safe_imports set whenever the source module is present in sys.stdlib_module_names and the name is absent from the UNSAFE_IMPORTS denylist, without inspecting what the name resolves to or how it behaves. The OvertlyBadEvals analysis pass in analysis.py then unconditionally skips any call whose function name appears in likely_safe_imports, including calls that would otherwise be flagged as overtly dangerous. As a result, any callable reachable through a non-blocked standard library module inherits module-level trust regardless of its own behavior, and check_safety() returns LIKELY_SAFE with zero findings for pickle payloads that reach code execution or file write through such callables. Demonstrated primitives: dataclasses._create_fn, which passes an attacker-controlled function body to exec() and yields arbitrary code execution on Python 3.7 through 3.12 (the internal _create_fn function was removed in Python 3.13); mailcap.findmatch, which internally calls os.system() on a test command taken from an attacker-controlled caps dictionary, yielding arbitrary code execution on Python versions through 3.12 (the mailcap module was removed in Python 3.13); and readline.add_history() followed by readline.write_history_file(), which writes attacker-controlled content to an arbitrary filesystem path (POSIX platforms, where the readline module is available). fickling.load() chains check_safety() into pickle.loads() as an explicit security gate, so a LIKELY_SAFE verdict causes the payload to be deserialized and executed with the privileges of the victim process. The root cause is the inference of callable safety from module origin; it is independent of, and separately fixable from, the dotted __qualname__ resolution weakness tracked as CVE-2026-118938, which this advisory does not address. As of 2026-10-30 the three demonstrated modules were added to UNSAFE_IMPORTS on the vendor master branch (commit d011709) pending release; released versions through 0.1.12 remain affected, and the module-origin trust root cause persists, as demonstrated by the related CVE-2026-118938 remaining exploitable on that same build.
Key facts
- Published
- 30 Oct 2026
- Last changed
- 6 Nov 2026
- Assigned by
- BombadilSystems
- EPSS
- 0.455% likely to be exploited in the next 30 days, higher than 39.993% of CVEs (scores for 16 Nov 2026)
- SSVC (CISA)
- Exploitation: none; Automatable: no; Technical impact: total
Severity scores
Each score is shown as its source gave it. They are not averaged or merged.
- 8.8CVSS 3.1, Highfrom the CNA (BombadilSystems)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Historical context and remediation
This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.
An attacker can craft a malicious pickle that invokes a dangerous callable imported from a standard library module not present in UNSAFE_IMPORTS. The name is added to likely_safe_imports by _process_import(), causing OvertlyBadEvals to skip the call, so check_safety() returns LIKELY_SAFE and fickling.load() proceeds to deserialize the payload. This yields arbitrary code execution via dataclasses._create_fn or mailcap.findmatch on Python versions through 3.12, and arbitrary file write with attacker-controlled content via readline.write_history_file on POSIX platforms across supported Python versions. Because the flaw is in the module-origin trust model rather than in any specific module list, adding the demonstrated modules to UNSAFE_IMPORTS does not address the root cause; additional dangerous callables remain reachable through other non-blocked standard library modules. (CNA impact statement)
No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.
Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| trailofbits | fickling |
|
Timeline
- 30 Oct 2026 Published