CVE-2026-22609·Python vulnerability
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.
- Severity
- high
- Software
- Python
- Fixed in
- 0.1.7
- Published
- 2026-01-10
Affected versions
Until: 0.1.7
Fixed in: 0.1.7
How to fix this CVE
Update Fickling to version 0.1.7 or later to restore proper detection of high-risk Python modules in pickle files. The vulnerable versions allow attackers to craft malicious pickles that bypass static safety analysis by importing dangerous modules without triggering security warnings. Ensure your Python environment and all pickle-processing dependencies are updated to prevent unauthorized code execution.
sudo dnf update python3-ficklingDefensia detects this vulnerability
How to check if you are affected
- Check Fickling version: python3 -c "import fickling; print(fickling.__version__)" and verify it is 0.1.7 or later
- Identify if Fickling is used in your environment: grep -r "from fickling" /path/to/your/code or pip list | grep fickling
- Review pickle processing logs for failed static analysis checks or unexpected module imports: grep -i 'unsafe\|import' /var/log/application.log
- Run a test pickle through Fickling's analyzer to confirm unsafe_imports() correctly flags dangerous modules: python3 -c "from fickling.pickle import Pickle; p = Pickle.load(open('test.pkl', 'rb')); print(p.unsafe_imports)"
FAQ
What is CVE-2026-22609?
This vulnerability affects Fickling's static analyzer, which failed to recognize several dangerous Python modules used for code execution. Attackers could craft malicious pickle files that import these undetected modules, bypassing Fickling's safety checks and potentially executing arbitrary code.
Is CVE-2026-22609 being actively exploited?
No, CVE-2026-22609 is not listed in the CISA Known Exploited Vulnerabilities catalog and no public exploits are currently available.
What versions of Fickling are affected by CVE-2026-22609?
All versions of Fickling prior to 0.1.7 are affected. Version 0.1.7 and later include fixes for unsafe_imports() detection.
How do I check if my server is vulnerable to CVE-2026-22609?
Run: python3 -c "import fickling; print(fickling.__version__)" If the version is below 0.1.7, your installation is vulnerable.
Does Defensia detect CVE-2026-22609?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Fickling is installed on a monitored server, CVE-2026-22609 will appear in your dashboard with remediation steps.
Related Python CVEs
References
- https://github.com/trailofbits/fickling/commit/29d5545e74b07766892c1f0461b801afccee4f91
- https://github.com/trailofbits/fickling/commit/9a2b3f89bd0598b528d62c10a64c1986fcb09f66
- https://github.com/trailofbits/fickling/commit/b793563e60a5e039c5837b09d7f4f6b92e6040d1
- https://github.com/trailofbits/fickling/commit/eb299b453342f1931c787bcb3bc33f3a03a173f9
- https://github.com/trailofbits/fickling/releases/tag/v0.1.7
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-22609. Free for 1 server.
Get started free