Security readout for executives and security teams
Plain-English summary
Fickling versions before 0.1.7 can incorrectly mark malicious Python pickle files as safe. If an organization relies on Fickling to screen untrusted pickle content, dangerous files may pass automated safety checks. The vendor patched the issue in version 0.1.7.
Executive priority
Prioritize remediation where Fickling protects ingestion of untrusted serialized Python data. This is a high-severity control-bypass issue, not merely a library hygiene update. Upgrade promptly, especially in automated analysis, data-processing, or security-review pipelines.
Technical view
The unsafe_imports() static analysis check used an incomplete dangerous-module blocklist. Malicious pickles importing omitted high-risk Python modules may bypass Fickling’s primary unsafe detection. The CVE maps to CWE-184 and CWE-502 and carries CVSS 4.0 score 8.9. Affected product is trailofbits/fickling before 0.1.7.
Likely exposure
Exposure is most likely where Fickling <0.1.7 evaluates pickle files from users, partners, downloads, repositories, or automated pipelines. Risk is lower where Fickling is not used as a trust decision or only processes fully controlled pickle inputs.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. The CVSS vector includes proof-of-concept exploit maturity, but no exploit details should be needed for remediation. The practical risk is a safety-control bypass before unsafe pickle handling.
Researcher notes
This is a static-analysis bypass caused by incomplete recognition of dangerous imports, not a new Python pickle primitive. Focus assessment on trust boundaries: whether Fickling’s unsafe_imports() result is used to permit later processing of pickle content. Evidence for affected range and patch comes from the GitHub advisory and v0.1.7 release references.
Mitigation direction
- Upgrade trailofbits/fickling to version 0.1.7 or later.
- Identify systems using Fickling as a pickle safety gate.
- Treat untrusted pickle files as unsafe until validation is complete.
- Review vendor advisory and release notes for any additional guidance.
Validation and detection
- Inventory installed Fickling versions across applications and pipelines.
- Confirm no deployment uses Fickling versions earlier than 0.1.7.
- Review workflows that accept external or user-supplied pickle files.
- Verify dependency lockfiles and container images reference the patched release.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-184: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-22609 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.9 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
8.9HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/trailofbits/fickling/security/advisories/GHSA-q5qq-mvfm-j35xCVE reference · x_refsource_CONFIRM
- https://github.com/trailofbits/fickling/commit/29d5545e74b07766892c1f0461b801afccee4f91CVE reference · x_refsource_MISC
- https://github.com/trailofbits/fickling/commit/9a2b3f89bd0598b528d62c10a64c1986fcb09f66CVE reference · x_refsource_MISC
- https://github.com/trailofbits/fickling/commit/b793563e60a5e039c5837b09d7f4f6b92e6040d1CVE reference · x_refsource_MISC
- https://github.com/trailofbits/fickling/commit/eb299b453342f1931c787bcb3bc33f3a03a173f9CVE reference · x_refsource_MISC
- https://github.com/trailofbits/fickling/releases/tag/v0.1.7CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incomplete List of Disallowed Inputs
Incomplete List of Disallowed Inputs represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.