Chaintrailofbits · ficklingPyPI:fickling
trailofbits fickling: variants (2025–2026)
5 CVEs over 3 generations, 16 Dec 2025 to 4 Jul 2026.
Family tree
Left to right by publication date.Oldest first. Select a CVE to open it.- CVE-2025-6774716 Dec 2025 First in the chain
- CVE-2025-6774816 Dec 2025 No direct link to an earlier CVE
- CVE-2026-2260610 Jan 2026 related to CVE-2025-67747related to CVE-2025-67748
- CVE-2026-2260710 Jan 2026 related to CVE-2025-67747related to CVE-2025-67748
- CVE-2026-145344 Jul 2026 variant of CVE-2025-67748variant of CVE-2026-22607
Exploited in the wild (CISA KEV) Not in KEV Priority score (0 to 100) High confidence Medium Low Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
CVEs in this family
Table view of the tree| CVE | Published | Title | Linked from | Priority |
|---|---|---|---|---|
| CVE-2025-67747 | 16 Dec 2025 | Fickling has missing detection for marshal.loads and types.FunctionType in unsafe modules list | First in chain | 9.0 |
| CVE-2025-67748 | 16 Dec 2025 | Fickling has Code Injection vulnerability via pty.spawn() | First in chain | 8.8 |
| CVE-2026-22606 | 10 Jan 2026 | Fickling has a bypass via runpy.run_path() and runpy.run_module() | CVE-2025-67747 · related · High | 14.5 |
| CVE-2026-22607 | 10 Jan 2026 | Fickling Blocklist Bypass: cProfile.run() | CVE-2025-67747 · related · High | 15.1 |
| CVE-2026-14534 | 4 Jul 2026 | Fickling check_safety() bypass via unlisted standard library modules (_posixsubprocess, site, atexit) · fixed in 0.1.11 | CVE-2025-67748 · variant in the same code · High | 15.8 |