CVE-2026-14534
Deserialization flaw in fickling enables code execution via pickle payloads.
Is CVE-2026-14534 being exploited?
Not confirmed. CVE-2026-14534 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.59% probability of exploitation in the next 30 days.
How severe is CVE-2026-14534?
CVE-2026-14534 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-14534?
Yes. A fix has been recorded for CVE-2026-14534. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-14534 affect?
CVE-2026-14534 affects fickling <=0.1.10 (Python library). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-14534?
Upgrade to fixed version when available; audit untrusted data usage
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
RCE via untrusted pickle data during fickling.load(); attacker can execute arbitrary code.
Immediate action required
- affected<= 0.1.10
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.