Technology · PyPI
fickling (PyPI) vulnerabilities
Updated . Rebuilt every hour.
Junglewise Threat Intelligence has tracked 16 vulnerabilities in fickling (PyPI): 0 in the last 7 days and 0 in the last 90 days, 0 of them critical and 0 exploited in the wild. The most recent, CVE-2026-22612, was published on 7 July 2026.
- Last 7 days
- 0
- Last 90 days
- 0
- Critical, all time
- 0
- Exploited in the wild
- 0
About fickling (PyPI)
A tool for analyzing and deconstructing Python pickle files to identify potential security risks.
Latest fickling (PyPI) vulnerabilities
- CVE-2026-22612: PYSEC-2026-1370 - Fickling vulnerable to detection bypass due to "builtins" blindnessmediumCVSS 4EPSS 0.3%
- CVE-2026-22609: PYSEC-2026-1372 - Fickling has Static Analysis Bypass via Incomplete Dangerous Module BlocklistmediumCVSS 4EPSS 0.6%
- CVE-2026-22608: PYSEC-2026-1369 - Fickling vulnerable to use of ctypes and pydoc gadget chain to bypass detectionmediumCVSS 4EPSS 0.4%
- CVE-2026-22607: PYSEC-2026-1371 - Fickling Blocklist Bypass: cProfile.run()mediumCVSS 4EPSS 0.5%
- CVE-2026-22606: PYSEC-2026-1373 - Fickling has a bypass via runpy.run_path() and runpy.run_module()mediumCVSS 4EPSS 0.5%
- CVE-2026-14535: Trail of Bits fickling protection bypass in MLAllowlist analysishighCVSS 8.8EPSS 0.6%
- CVE-2026-14534: Trail of Bits fickling sandbox bypass via incomplete denylisthighCVSS 8.8EPSS 0.6%
- fickling's `platform` module subprocess invocation evades `check_safety()` with `LIKELY_SAFE`mediumCVSS 4
- fickling modules linecache, difflib and gc are missing from the unsafe modules blocklistmediumCVSS 4
- Fickling missing RCE-capable modules in UNSAFE_IMPORTSmediumCVSS 4
- Fickling has `always_check_safety()` bypass: pickle.loads and _pickle.loads remain unhookedmediumCVSS 4
- Fickling has safety check bypass via REDUCE+BUILD opcode sequencemediumCVSS 4
- Fickling: OBJ opcode call invisibility bypasses all safety checksmediumCVSS 4
- Fickling has a detection bypass via stdlib network-protocol constructorsmediumCVSS 4
- CVE-2025-67748: Trail of Bits Fickling code injection via pty.spawn bypasshighCVSS 7.8EPSS 0.3%
- CVE-2025-67747: PYSEC-2026-1368 - Fickling has missing detection for marshal.loads and types.FunctionType in unsafe modules listhighCVSS 7.8EPSS 0.3%
Most severe fickling (PyPI) vulnerabilities
Exploited in the wild first, then by severity and CVSS score.
- CVE-2026-14534: Trail of Bits fickling sandbox bypass via incomplete denylisthighCVSS 8.8EPSS 0.6%
- CVE-2026-14535: Trail of Bits fickling protection bypass in MLAllowlist analysishighCVSS 8.8EPSS 0.6%
- CVE-2025-67747: PYSEC-2026-1368 - Fickling has missing detection for marshal.loads and types.FunctionType in unsafe modules listhighCVSS 7.8EPSS 0.3%
- CVE-2025-67748: Trail of Bits Fickling code injection via pty.spawn bypasshighCVSS 7.8EPSS 0.3%
- CVE-2026-22609: PYSEC-2026-1372 - Fickling has Static Analysis Bypass via Incomplete Dangerous Module BlocklistmediumCVSS 4EPSS 0.6%
- CVE-2026-22607: PYSEC-2026-1371 - Fickling Blocklist Bypass: cProfile.run()mediumCVSS 4EPSS 0.5%
- CVE-2026-22606: PYSEC-2026-1373 - Fickling has a bypass via runpy.run_path() and runpy.run_module()mediumCVSS 4EPSS 0.5%
- CVE-2026-22608: PYSEC-2026-1369 - Fickling vulnerable to use of ctypes and pydoc gadget chain to bypass detectionmediumCVSS 4EPSS 0.4%
- CVE-2026-22612: PYSEC-2026-1370 - Fickling vulnerable to detection bypass due to "builtins" blindnessmediumCVSS 4EPSS 0.3%
- fickling's `platform` module subprocess invocation evades `check_safety()` with `LIKELY_SAFE`mediumCVSS 4
Vulnerabilities per week
Nothing was published in the last eight weeks. The last 13 weeks, by the week each vulnerability was published.
| Week of | Bar | Vulns | Critical |
|---|---|---|---|
| 17 Aug 2026 | 0 | 0 | |
| 24 Aug 2026 | 0 | 0 | |
| 31 Aug 2026 | 0 | 0 | |
| 7 Sep 2026 | 0 | 0 | |
| 14 Sep 2026 | 0 | 0 | |
| 21 Sep 2026 | 0 | 0 | |
| 28 Sep 2026 | 0 | 0 | |
| 5 Oct 2026 | 0 | 0 | |
| 12 Oct 2026 | 0 | 0 | |
| 19 Oct 2026 | 0 | 0 | |
| 26 Oct 2026 | 0 | 0 | |
| 2 Nov 2026 | 0 | 0 | |
| 9 Nov 2026 | 0 | 0 |
Embed a badge
A live badge for a README, a status page or an internal wiki: how many fickling (PyPI) vulnerabilities were published in the last 7 days and how many of them are critical, refreshed hourly.
[](https://junglewise.ai/threats/technologies/fickling)<a href="https://junglewise.ai/threats/technologies/fickling"><img src="https://junglewise.ai/threats/technologies/fickling/badge.svg" alt="fickling (PyPI) vulnerabilities" /></a>How this is built
Junglewise Threat Intelligence collects vulnerabilities from NVD, GitHub Security Advisories, OSV, the CISA Known Exploited Vulnerabilities catalog, FIRST EPSS and vendor advisories, and matches each one to the technologies and vendors it affects. Dates are the date a vulnerability was published, in UTC.
The pages are rebuilt from the database every hour. Frozen weekly and monthly reports never change once published, so they can be cited.
Use this data
The same data is at https://junglewise.ai/threats/technologies/fickling.json, and this page as text at https://junglewise.ai/threats/technologies/fickling.md, for scripts and language models. It is free to reuse under CC BY 4.0 with a link back to this page.
Cite as: Junglewise Threat Intelligence, "fickling (PyPI) vulnerabilities", https://junglewise.ai/threats/technologies/fickling, 13 November 2026.