UTC
High

OpenClaw Telegram webhook request bodies were read before secret validation, enabling unauthenticated resource exhaustion

CVE-2026-32980 · GHSA-jq3f-vjww-8rq7 · published 2026-03-16 · updated 2026-04-01

Severity
High
CVSS score
7.5
Chance of exploitation (EPSS)
0.55%
Fixed in
2026.3.13
  • Exploitation No known exploitation
  • Automatable No
  • Technical impact Partial
  • CISA SSVC
What it is

openclaw versions <= 2026.3.12 read and buffered Telegram webhook request bodies before validating x-telegram-bot-api-secret-token. This let unauthenticated callers force up to the configured webhook body limit of pre-auth body I/O and JSON parse work per request.

What to do

Upgrade openclaw to 2026.3.13 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.

[email protected] validates the Telegram webhook secret before any body I/O. Current code reads the header, rejects invalid requests immediately with 401, and only calls readJsonBodyWithLimit(...) after hasValidTelegramWebhookSecret(...) succeeds. Regression coverage exists in src/telegram/webhook.test.ts ( ).

Affected
PackageRegistryAffectedFixed in
openclawnpm<= 2026.3.122026.3.13

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