How severe is CVE-2026-22606?

CVE-2026-22606 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2026-22606 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (39th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-22606?

CVE-2026-22606 affects Trailofbits Fickling. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-22606?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2026-22606 have an EU (EUVD) identifier?

Yes. CVE-2026-22606 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-1688.

When was CVE-2026-22606 published?

CVE-2026-22606 was published on 2026-01-10 and last updated on 2026-06-17.

CVE-2026-22606

CVE-2026-22606 is a high-severity vulnerability in Trailofbits Fickling with a CVSS 3.x base score of 7.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-184.

Key facts

Severity: High (CVSS 3.x base score 7.8)
CVSS v4: 8.9
EPSS exploit prediction: 0% (39th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-1688
Weakness: CWE-184
Affected product: Trailofbits Fickling
Published: 2026-01-10
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2026-22606?: 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.
How severe is CVE-2026-22606?: CVE-2026-22606 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-22606 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (39th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-22606?: CVE-2026-22606 affects Trailofbits Fickling. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-22606?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-22606 have an EU (EUVD) identifier?: Yes. CVE-2026-22606 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-1688.
When was CVE-2026-22606 published?: CVE-2026-22606 was published on 2026-01-10 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:trailofbits:fickling:*:*:*:*:*:python:*:*

More vulnerabilities in Trailofbits Fickling

CVE-2026-14535 — High (CVSS 8.8): In Trail of Bits fickling versions up to and including 0.1.11, the UnsafeImportsML analysis pass unconditionally calls…
CVE-2026-14534 — High (CVSS 8.8): Trail of Bits fickling versions up to and including 0.1.10 do not include the Python standard library modules…
CVE-2026-22612 — High (CVSS 7.8): Fickling is a Python pickling decompiler and static analyzer. Prior to version 0.1.7, Fickling is vulnerable to…
CVE-2026-22609 — High (CVSS 7.8): Fickling is a Python pickling decompiler and static analyzer. Prior to version 0.1.7, the unsafe_imports() method in…
CVE-2026-22608 — High (CVSS 7.8): Fickling is a Python pickling decompiler and static analyzer. Prior to version 0.1.7, both ctypes and pydoc modules…
CVE-2026-22607 — High (CVSS 7.8): Fickling is a Python pickling decompiler and static analyzer. Fickling versions up to and including 0.1.6 do not treat…

All CVEs affecting Trailofbits Fickling →

Other CWE-184 vulnerabilities

CVE-2026-87985 — Critical (CVSS 10.0): An arbitrary code execution vulnerability in Mistral Vibe allows an attacker to bypass command permission checks using…
CVE-2026-79696 — Critical (CVSS 10.0): A Code Injection vulnerability in adk web in Google Cloud Agent Development Kit (ADK) for Python versions 2.0.0 through…
CVE-2026-57138 — Critical (CVSS 9.9): PraisonAI is a multi-agent teams system. From 1.4.0 until 1.7.2, codeMode in…
CVE-2026-65083 — Critical (CVSS 9.9): NVIDIA OpenShell for Linux contains a vulnerability in its sandbox provisioning API, where an attacker could cause an…
CVE-2026-47392 — Critical (CVSS 9.9): PraisonAI is a multi-agent teams system. Prior to version 4.6.40 of PraisonAI, corresponding to version 1.6.40 of…
CVE-2026-28363 — Critical (CVSS 9.9): In OpenClaw before 2026.2.23, tools.exec.safeBins validation for sort could be bypassed via GNU long-option…

Browse all CWE-184 vulnerabilities →