UTC
Medium

OpenClaw: Unauthorized Telegram Senders Trigger Media Download and Disk Write Before Access Check

GHSA-h656-5vcf-cm23 · published 2026-03-03

Severity
Medium
CVSS score
Not scored
Chance of exploitation (EPSS)
No CVE
Fixed in
2026.2.24
What it is

In Telegram DM mode, inbound media was downloaded and written to disk before sender authorization checks completed. An unauthorized sender could trigger inbound media download/write activity (including media groups) even when DM access should be denied.

What to do

Upgrade openclaw to 2026.2.24 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

9514201fb9b51de5d0b23151110d0ff5d9c8bd67

Affected
PackageRegistryAffectedFixed in
openclawnpm<= 2026.2.232026.2.24

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