UTC

fickling

14 published advisories; version 0.1.10 or later fixes all of them.

Registry
PyPI
Advisories
14
Latest fix
0.1.10
Exploited in the wild
None listed

Check your projects

shieldpi agent-config checks agent and MCP packages from npm and PyPI, not fickling. Any scanner that reads the OSV database finds it in your lockfiles, for example Google's open-source OSV-Scanner.

osv-scanner scan source -r .

Or check a lockfile against ShieldMap in your browser.

Malicious lookalikes

Packages reported malicious by OpenSSF whose names imitate fickling. Check that you install fickling itself.

All AI lookalikes →
Provenance

Source: github.com/trailofbits/fickling, named in the package metadata (not verified)

10 of the last 10 releases of fickling were published with build provenance: a signed record of the repository and commit each was built from, which the registry checks before it accepts the release.

  • 0.1.13
  • 0.1.12
  • 0.1.11
  • 0.1.10
  • 0.1.9
  • 0.1.8
  • 0.1.7
  • 0.1.6
  • 0.1.5
  • 0.1.4

Green: published with provenance. Grey: without.

OpenSSF Scorecard: 7.8 of 10 on 2026-10-19.

No dangerous CI workflows
10/10
CI tokens read-only by default
10/10
Build dependencies pinned
8/10
Branch protection
Not checked
Changes reviewed before merge
2/10
Signed releases
Not checked
Actively maintained
10/10
Security policy
10/10
Full Scorecard →

Provenance from deps.dev (CC BY 4.0); Scorecard from OpenSSF (CDLA-Permissive-2.0). As of 2026-11-18.

Advisories
AdvisorySeverityAffectedFixed inPublished
fickling's `platform` module subprocess invocation evades `check_safety()` with `LIKELY_SAFE`GHSA-5cxw-w2xg-2m8hMedium<= 0.1.90.1.102026-03-13
fickling modules linecache, difflib and gc are missing from the unsafe modules blocklistGHSA-r48f-3986-4f9cMedium<= 0.1.90.1.102026-03-13
Fickling missing RCE-capable modules in UNSAFE_IMPORTSGHSA-5hwf-rc88-82xmHigh<= 0.1.80.1.92026-03-04
Fickling has `always_check_safety()` bypass: pickle.loads and _pickle.loads remain unhookedGHSA-wccx-j62j-r448High<= 0.1.80.1.92026-03-04
Fickling has safety check bypass via REDUCE+BUILD opcode sequenceGHSA-mhc9-48gj-9gp3Medium<= 0.1.70.1.82026-02-25
Fickling: OBJ opcode call invisibility bypasses all safety checksGHSA-mxhj-88fx-4pcvHigh< 0.1.80.1.82026-02-24
Fickling has a detection bypass via stdlib network-protocol constructorsGHSA-83pf-v6qq-pwmrLow<= 0.1.70.1.82026-02-20
Fickling vulnerable to use of ctypes and pydoc gadget chain to bypass detectionCVE-2026-22608High<= 0.1.60.1.72026-01-09
Fickling vulnerable to detection bypass due to "builtins" blindnessCVE-2026-22612High<= 0.1.60.1.72026-01-09
Fickling Blocklist Bypass: cProfile.run()CVE-2026-22607High<= 0.1.60.1.72026-01-09
Fickling has Static Analysis Bypass via Incomplete Dangerous Module BlocklistCVE-2026-22609High<= 0.1.60.1.72026-01-09
Fickling has a bypass via runpy.run_path() and runpy.run_module()CVE-2026-22606High<= 0.1.60.1.72026-01-09
Fickling has missing detection for marshal.loads and types.FunctionType in unsafe modules listCVE-2025-67747High< 0.1.60.1.62025-12-15
Fickling has Code Injection vulnerability via pty.spawn()CVE-2025-67748High< 0.1.60.1.62025-12-15

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].