# Fickling has a bypass via runpy.run_path() and runpy.run_module()

Advisory record · `GHSA-wfq2-52f7-7qvj`

- **Identifiers:** `GHSA-wfq2-52f7-7qvj` · `CVE-2026-22606` · `PYSEC-2026-1373`
- **State:** Confirmed
- **Severity:** CVSS 8.9 High
- **Critical:** No
- **Weakness (CWE):** [CWE-184](https://cwe.mitre.org/data/definitions/184.html) · [CWE-502](https://cwe.mitre.org/data/definitions/502.html)
- **Tags:** [Insecure deserialization](https://agentprime.io/advisories/tag/deserialization.md) · [CWE-184](https://agentprime.io/advisories/tag/cwe-184.md)
- **Published:** 9 Jan 2026
- **Updated:** 7 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 9 Jan 2026, 20:52 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

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

## 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.9 High, CVSS 4.0: `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`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0048, the 41st percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 9 Jan 2026. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-wfq2-52f7-7qvj](https://github.com/advisories/GHSA-wfq2-52f7-7qvj)
- [OSV: GHSA-wfq2-52f7-7qvj](https://osv.dev/vulnerability/GHSA-wfq2-52f7-7qvj)
- <https://github.com/trailofbits/fickling/security/advisories/GHSA-565g-hwwr-4pp3>
- <https://github.com/trailofbits/fickling/security/advisories/GHSA-r7v6-mfhq-g3m2>
- <https://github.com/trailofbits/fickling/security/advisories/GHSA-wfq2-52f7-7qvj>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-22606>
- <https://github.com/trailofbits/fickling/pull/108>
- <https://github.com/trailofbits/fickling/pull/187>
- <https://github.com/trailofbits/fickling/pull/195>
- <https://github.com/trailofbits/fickling/commit/9a2b3f89bd0598b528d62c10a64c1986fcb09f66>
- <https://github.com/trailofbits/fickling>
- <https://github.com/trailofbits/fickling/blob/977b0769c13537cd96549c12bb537f05464cf09c/test/test_bypasses.py#L87>
- <https://github.com/trailofbits/fickling/releases/tag/v0.1.7>

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-wfq2-52f7-7qvj>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-wfq2-52f7-7qvj/>. Everything for agents: <https://agentprime.io/llms.txt>.