CVE-2026-14534
HIGHDescription
Trail of Bits fickling versions up to and including 0.1.10 do not include the Python standard library modules _posixsubprocess, site, and atexit in the UNSAFE_IMPORTS denylist (fickle.py). Because these modules are absent from the denylist, fickling's check_safety() function returns LIKELY_SAFE with zero findings for pickle payloads that invoke dangerous functions including _posixsubprocess.fork_exec (C-level process spawner capable of executing arbitrary binaries), site.execsitecustomize (executes arbitrary site customization code), and atexit._run_exitfuncs (triggers all registered exit handler callbacks). The fickling.load() API chains check_safety() into pickle.loads() as an explicit security gate; a LIKELY_SAFE verdict causes the payload to be deserialized and executed. This shares the same root cause as CVE-2026-22607 (cProfile), CVE-2025-67748 (pty), and CVE-2025-67747 (marshal/types). OvertlyBadEvals does not flag these modules because they are standard library imports. UnsafeImports does not flag them because they are not in the denylist. The UnusedVariables heuristic is defeated by the SETITEMS opcode pattern.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 29% of all known CVEs.
References
Related Vulnerabilities
Other CWE-184 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2024-5217 | Critical | 9.8 | 100% | KEV | - |
| CVE-2022-43396 | High | 8.8 | 55% | - | Fix |
| CVE-2017-7525 | Critical | 9.8 | 38% | - | Fix |
| CVE-2024-5178 | Medium | 4.9 | 34% | - | - |
| CVE-2018-7489 | Critical | 9.8 | 20% | - | Fix |
| CVE-2018-6383 | High | 8.8 | 13% | - | - |
Common questions
How do I fix CVE-2026-14534?
No published fix for CVE-2026-14534 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-14534 being actively exploited?
Not that we know of. CVE-2026-14534 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.37% is the estimated probability that it will be exploited in the next 30 days. That is higher than 29% of all scored CVEs.
How severe is CVE-2026-14534?
CVE-2026-14534 has a CVSS v3 base score of 8.8, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-14534
Markdown
[](https://tridentstack.com/cve/CVE-2026-14534)HTML
<a href="https://tridentstack.com/cve/CVE-2026-14534"><img src="https://tridentstack.com/cve/badge/CVE-2026-14534.svg" alt="CVE-2026-14534"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-07-10.