Security readout for executives and security teams
Plain-English summary
Fickling may understate the danger of a malicious Python pickle. Versions before 0.1.7 classify certain unsafe behavior as “suspicious” rather than clearly malicious. If teams use Fickling as an allow/deny security gate before deserializing pickles, attackers could trick users or systems into running untrusted code.
Executive priority
Prioritize remediation where Fickling protects pickle deserialization in automated or user-facing workflows. The business risk is code execution from data files that appear less dangerous than they are. Upgrade promptly, especially in ML, data science, and CI environments handling external artifacts.
Technical view
CVE-2026-22607 is a blocklist bypass in Trail of Bits Fickling. Versions up to and including 0.1.6 do not treat Python’s cProfile module as unsafe, so pickles using cProfile.run() are labeled SUSPICIOUS instead of OVERTLY_MALICIOUS. The issue maps to CWE-184 and CWE-502 and is patched in 0.1.7.
Likely exposure
Exposure is most likely in Python workflows, CI pipelines, ML/model handling, or products that scan pickle files with Fickling before deciding whether to deserialize them. Systems not using Fickling, or not deserializing untrusted pickle data, are not directly exposed based on the provided sources.
Exploitation context
The sources describe a path where misclassification can lead a user or system to deserialize attacker-controlled pickle data. The CVSS vector indicates network reachability and low attack complexity. The CVE is not marked as CISA KEV, and the provided sources do not state active exploitation in the wild.
Researcher notes
This is a classification weakness, not a parser crash. The security impact depends on downstream trust decisions after Fickling labels a pickle SUSPICIOUS. The patch adds cProfile handling to the unsafe blocklist. Evidence is limited to the advisory, CVE record, commit, and release notes provided.
Mitigation direction
- Upgrade Fickling to version 0.1.7 or later.
- Identify products or pipelines using Fickling as a pickle security gate.
- Treat SUSPICIOUS pickle results as unsafe until reviewed.
- Avoid deserializing untrusted pickle files where possible.
- Review vendor advisory and release notes for implementation guidance.
Validation and detection
- Inventory installed Fickling versions across development and production environments.
- Confirm no deployed environment uses Fickling 0.1.6 or earlier.
- Review workflows that deserialize pickle data after Fickling analysis.
- Check dependency lockfiles and container images for vulnerable Fickling versions.
- Verify upgrade to 0.1.7 through package metadata or software composition analysis.
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 lookupCVE-2026-22607 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-p523-jq9w-64x9CVE reference · x_refsource_CONFIRM
- https://github.com/trailofbits/fickling/commit/dc8ae12966edee27a78fe05c5745171a2b138d43CVE 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.