{"cve":"CVE-2026-14535","nvd":{"published":"2026-07-04T14:16:29.063","modified":"2026-10-25T15:10:00.147","status":"Analyzed","description":"In Trail of Bits fickling versions up to and including 0.1.11, the UnsafeImportsML analysis pass unconditionally calls AnalysisContext.shorten_code(node) on every import node it inspects, regardless of whether the import is flagged as unsafe. This call registers the shortened code representation in the shared AnalysisContext.reported_shortened_code set. When the MLAllowlist analysis pass subsequently runs, it calls the same shorten_code() method, receives already_reported=True for every import, and executes a continue statement that skips its allowlist check entirely. This renders MLAllowlist dead code for all imports — it never evaluates whether an import is in the ML allowlist or not. The MLAllowlist pass was designed to catch imports of modules outside the known-safe ML ecosystem (torch, numpy, transformers, etc.) that slip past the UnsafeImports denylist. With MLAllowlist inoperative, any standard library module not in the UNSAFE_IMPORTS denylist can be invoked via pickle deserialization while fickling's check_safety() returns LIKELY_SAFE. The fickling.load() API chains check_safety() into pickle.loads() as an explicit security gate, meaning a LIKELY_SAFE verdict causes the payload to be deserialized and executed. The root cause is shared mutable state between independently-correct analysis passes — UnsafeImportsML works as designed in isolation, MLAllowlist works as designed in isolation, but the shared reported_shortened_code set causes UnsafeImportsML to poison MLAllowlist's deduplication logic.","cvss_v4":null,"cvss_v3":{"version":"3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","score":9.8},"cwes":["CWE-693"],"references":["https://github.com/trailofbits/fickling/commit/41ce7cb01edd97072994039574a2301ebb3f463d","https://github.com/trailofbits/fickling/pull/278","https://github.com/trailofbits/fickling/releases/tag/v0.1.12","https://github.com/trailofbits/fickling/security/advisories/GHSA-cffv-grgg-g429","https://github.com/trailofbits/fickling/security/advisories/GHSA-cffv-grgg-g429"],"products":["trailofbits:fickling"],"source":"nvd","synced_at":"2026-10-25T17:50:06.907763985+00:00"},"epss":{"cve":"CVE-2026-14535","score":0.00564,"percentile":0.46625,"date":"2026-10-25"},"kev":null,"osv":[{"id":"PYSEC-2026-2150","url":"https://osv.dev/vulnerability/PYSEC-2026-2150","summary":"","modified":"2026-07-13T07:15:25.026515566Z","packages":[{"ecosystem":"PyPI","name":"fickling","purl":"pkg:pypi/fickling","ranges":["<0.1.12"],"fixed":["0.1.12"]}]}],"attribution":["This product uses the NVD API but is not endorsed or certified by the NVD.","EPSS scores: FIRST Exploit Prediction Scoring System, https://www.first.org/epss","Known exploited vulnerabilities: CISA Known Exploited Vulnerabilities Catalog, https://www.cisa.gov/known-exploited-vulnerabilities-catalog","Package advisories: OSV (https://osv.dev), from the GitHub Advisory Database, PyPA, Go, RustSec and other ecosystem databases, under CC-BY 4.0 or CC0","CVE records: the CVE Program's CVE List (https://www.cve.org), under its terms of use (https://www.cve.org/Legal/TermsOfUse). CVE is a registered trademark of The MITRE Corporation; this product is not affiliated with the CVE Program."]}