CVE-2026-22609 Fickling has Static Analysis Bypass via Incomplete Dangerous Module Blocklist

High 8.9 Published Updated

Attackers can bypass Fickling's static analysis to execute arbitrary code via malicious pickles importing unblocked dangerous modules.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-22609?

CVE-2026-22609 is a high-severity unsafe deserialization vulnerability in trailofbits fickling, published on 10 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

Fickling is a Python pickling decompiler and static analyzer. Prior to version 0.1.7, the unsafe_imports() method in Fickling's static analyzer fails to flag several high-risk Python modules that can be used for arbitrary code execution. Malicious pickles importing these modules will not be detected as unsafe, allowing attackers to bypass Fickling's primary static safety checks. This issue has been patched in version 0.1.7.

Weakness: CWE-502, CWE-184

Which versions are affected by CVE-2026-22609?

3 open source packages ship an affected version, including fickling. It affects 1 product.

PackageAffectedFixed in
fickling PyPIAll versions0.1.7
fickling PyPIAll versions0.1.7
fickling PyPIAll versions0.1.7

Products include Trailofbits Fickling.

How do I fix CVE-2026-22609?

Upgrade fickling to 0.1.7 or later.

Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.

Is CVE-2026-22609 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-22609 exists.

Sources

Also known as GHSA-q5qq-mvfm-j35x, PYSEC-2026-1372.

Is CVE-2026-22609 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free