UTC
Critical

PickleScan's profile.run blocklist mismatch allows exec() bypass

CVE-2026-53873 · GHSA-7wx9-6375-f5wh · published 2026-03-03 · updated 2026-06-18

Severity
Critical
CVSS score
9.8
Chance of exploitation (EPSS)
0.46%
Fixed in
1.0.4
  • Exploitation Public proof of concept
  • Automatable Yes
  • Technical impact Total
  • CISA SSVC
What it is

profile.run() provides direct exec() execution. An attacker can execute arbitrary Python code while picklescan reports no issues. This is particularly impactful because exec() can import any module and call any function, bypassing the blocklist entirely.

What to do

Upgrade picklescan to 1.0.4 or later.

Change the profile blocklist entry from: to: Or explicitly add the module-level functions:

Affected
PackageRegistryAffectedFixed in
picklescanPyPI< 1.0.41.0.4

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

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].