# fickling (PyPI) vulnerabilities 11 known vulnerabilities (11 high), with the versions each affects and the releases that fix them. ## At a glance - Latest release: 0.1.13 (Nov 3, 2026): no advisory affects it - Newest unaffected release: 0.1.13 (Nov 3, 2026), the latest release - Weekly downloads: 178.9K - Dependents: 63 - Releases: 20 since 0.0.1 (Mar 8, 2021) - Registry: https://pypi.org/project/fickling/ - Releases read: Nov 8, 2026 ## Version timeline Affected versions per advisory, in version order: - CVE-2026-118938: 0.0.1 to 0.1.12 (0.1.13 is outside it) - CVE-2026-16760: 0.0.1 to 0.1.12 (0.1.13 is outside it) - CVE-2026-14535: 0.0.1 to 0.1.11 (0.1.12 is outside it) - CVE-2026-14534: 0.0.1 to 0.1.10 (0.1.11 is outside it) - CVE-2026-22612: 0.0.1 to 0.1.6 (0.1.7 is outside it) - CVE-2026-22609: 0.0.1 to 0.1.6 (0.1.7 is outside it) - CVE-2026-22608: 0.0.1 to 0.1.6 (0.1.7 is outside it) - CVE-2026-22607: 0.0.1 to 0.1.6 (0.1.7 is outside it) - CVE-2026-22606: 0.0.1 to 0.1.6 (0.1.7 is outside it) - CVE-2025-67748: 0.0.1 to 0.1.5 (0.1.6 is outside it) - CVE-2025-67747: 0.0.1 to 0.1.5 (0.1.6 is outside it) ## Advisories (11) ### [CVE-2026-118938](https://cve.now/CVE-2026-118938): Fickling check\_safety() bypass: dotted qualname in STACK\_GLOBAL resolves a class-method attribute path that evades call analysis - Severity: High 8.8 - Published: Oct 30, 2026 - Affected: through 0.1.12. - Fixed in 0.1.13 (released Nov 3, 2026, 4 days after disclosure), the first release outside every affected range (no listed fixed version clears them all). - The latest release, 0.1.13, is not affected. ### [CVE-2026-16760](https://cve.now/CVE-2026-16760): Fickling check\_safety() bypass: likely\_safe\_imports grants module-origin trust to unvalidated standard library callables - Severity: High 8.8 - Published: Oct 30, 2026 - Affected: through 0.1.12. - Fixed in 0.1.13 (released Nov 3, 2026, 4 days after disclosure), the first release outside every affected range (no listed fixed version clears them all). - The latest release, 0.1.13, is not affected. ### [CVE-2026-14535](https://cve.now/CVE-2026-14535): Fickling MLAllowlist analysis pass rendered inoperative by shared mutable state in AnalysisContext.shorten\_code() - Severity: High 8.8 - Published: Jul 4, 2026 - Affected: through 0.1.11; fixed in 0.1.12. - Fixed in 0.1.12 (released Jun 26, 2026, 8 days before disclosure). - The latest release, 0.1.13, is not affected. ### [CVE-2026-14534](https://cve.now/CVE-2026-14534): Fickling check\_safety() bypass via unlisted standard library modules (\_posixsubprocess, site, atexit) - Severity: High 8.8 - Published: Jul 4, 2026 - Affected: through 0.1.10; fixed in 0.1.11. - Fixed in 0.1.11 (released May 6, 2026, 59 days before disclosure). - The latest release, 0.1.13, is not affected. ### [CVE-2026-22612](https://cve.now/CVE-2026-22612): Fickling vulnerable to detection bypass due to "builtins" blindness - Severity: High 8.9 - Published: Jan 10, 2026 - Affected: fixed in 0.1.7. - Fixed in 0.1.7 (released Jan 9, 2026, 1 day before disclosure). - The latest release, 0.1.13, is not affected. ### [CVE-2026-22609](https://cve.now/CVE-2026-22609): Fickling has Static Analysis Bypass via Incomplete Dangerous Module Blocklist - Severity: High 8.9 - Published: Jan 10, 2026 - Affected: fixed in 0.1.7. - Fixed in 0.1.7 (released Jan 9, 2026, 1 day before disclosure). - The latest release, 0.1.13, is not affected. ### [CVE-2026-22608](https://cve.now/CVE-2026-22608): Fickling vulnerable to use of ctypes and pydoc gadget chain to bypass detection - Severity: High 8.9 - Published: Jan 10, 2026 - Affected: fixed in 0.1.7. - Fixed in 0.1.7 (released Jan 9, 2026, 1 day before disclosure). - The latest release, 0.1.13, is not affected. ### [CVE-2026-22607](https://cve.now/CVE-2026-22607): Fickling Blocklist Bypass: cProfile.run() - Severity: High 8.9 - Published: Jan 10, 2026 - Affected: fixed in 0.1.7. - Fixed in 0.1.7 (released Jan 9, 2026, 1 day before disclosure). - The latest release, 0.1.13, is not affected. ### [CVE-2026-22606](https://cve.now/CVE-2026-22606): Fickling has a bypass via runpy.run\_path() and runpy.run\_module() - Severity: High 8.9 - Published: Jan 10, 2026 - Affected: fixed in 0.1.7. - Fixed in 0.1.7 (released Jan 9, 2026, 1 day before disclosure). - The latest release, 0.1.13, is not affected. ### [CVE-2025-67748](https://cve.now/CVE-2025-67748): Fickling has Code Injection vulnerability via pty.spawn() - Severity: High 7.1 - Published: Dec 16, 2025 - Affected: fixed in 0.1.6. - Fixed in 0.1.6 (released Dec 15, 2025, 1 day before disclosure). - The latest release, 0.1.13, is not affected. ### [CVE-2025-67747](https://cve.now/CVE-2025-67747): Fickling has missing detection for marshal.loads and types.FunctionType in unsafe modules list - Severity: High 7.1 - Published: Dec 16, 2025 - Affected: fixed in 0.1.6. - Fixed in 0.1.6 (released Dec 15, 2025, 1 day before disclosure). - The latest release, 0.1.13, is not affected. --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/packages/pypi/fickling Site guide for agents: https://cve.now/llms.txt Uses NVD data; not endorsed by NVD.