# 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, regardles...

Advisory record · `GHSA-cffv-grgg-g429`

- **Identifiers:** `GHSA-cffv-grgg-g429` · `CVE-2026-14535` · `PYSEC-2026-2150`
- **State:** Confirmed
- **Severity:** CVSS 8.8 High
- **Critical:** No
- **Weakness (CWE):** [CWE-693](https://cwe.mitre.org/data/definitions/693.html)
- **Tags:** [CWE-693](https://agentprime.io/advisories/tag/cwe-693.md)
- **Published:** 4 Jul 2026
- **Updated:** 13 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 4 Jul 2026, 14:16 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `fickling` (PyPI): affected `<0.1.12`; fixed in `0.1.12`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Fickling versions up to and including 0.1.11 are vulnerable. The UnsafeImportsML analysis pass records every import it inspects in a shared set, which causes the MLAllowlist pass to skip its allowlist check entirely. An attacker who can supply a pickle file to a system that uses fickling's check_safety() or fickling.load() can get a malicious payload past the safety check using any standard library module not on the denylist, which may then execute when deserialized. Upgrade to fickling 0.1.12 or later.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.8 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`, from CNA (BombadilSystems)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0056, the 47th percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:04 UTC: First seen by agentprime
- 31 Oct 2026, 15:04 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/PYSEC-2026-2150)

## Sources

- [GitHub Advisory Database: GHSA-cffv-grgg-g429](https://github.com/advisories/GHSA-cffv-grgg-g429)
- [OSV: GHSA-cffv-grgg-g429](https://osv.dev/vulnerability/GHSA-cffv-grgg-g429)
- <https://github.com/trailofbits/fickling/releases/tag/v0.1.12>
- <https://github.com/trailofbits/fickling/commit/41ce7cb01edd97072994039574a2301ebb3f463d>
- <https://github.com/trailofbits/fickling/pull/278>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-cffv-grgg-g429>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-cffv-grgg-g429/>. Everything for agents: <https://agentprime.io/llms.txt>.
