Code execution via MLAllowlist shared-state pollution
Published Jul 4, 2026 · Updated Jul 4, 2026
Protection bypass in Trail of Bits Fickling 0.1.11 and earlier allows attackers to execute code through a crafted pickle file. UnsafeImportsML records every import through AnalysisContext.shorten_code(), causing MLAllowlist to treat each later import as already reported and skip its allowlist check. Execution requires the MLAllowlist pass to share an analysis context with the earlier pass and the consuming application to deserialize a payload after a LIKELY_SAFE result.
Summary
What happened
Protection bypass in Trail of Bits Fickling 0.1.11 and earlier allows attackers to execute code through a crafted pickle file. UnsafeImportsML records every import through AnalysisContext.shorten_code(), causing MLAllowlist to treat each later import as already reported and skip its allowlist check. Execution requires the MLAllowlist pass to share an analysis context with the earlier pass and the consuming application to deserialize a payload after a LIKELY_SAFE result.
The record
- CVE
- CVE-2026-14535
- Published
- Jul 4, 2026
- Updated
- Jul 4, 2026
- Vendor
- Trail of Bits
- Product
- Fickling
- Classifications
- CWE-693, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 4, 2026CVE publishedPublication date reported by the CVE source.
- Jul 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=0.1.11
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- MLAllowlist shared-state bypass proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo