UTC
Medium

OpenClaw Telegram allowlist authorization accepted mutable usernames

CVE-2026-28480 · GHSA-mj5r-hh7j-4gxf · published 2026-02-18 · updated 2026-03-06

Severity
Medium
CVSS score
5.9
Chance of exploitation (EPSS)
0.24%
Fixed in
Not in every package
  • Exploitation No known exploitation
  • Automatable Yes
  • Technical impact Partial
  • CISA SSVC
What it is

Operators who treat Telegram allowlists as strict identity controls could unintentionally grant access if a username changes hands (identity rebinding/spoof risk). This can allow an unauthorized sender to interact with the bot in allowlist mode.

What to do

Upgrade openclaw to 2026.2.14 or later. No fixed release is listed yet for clawdbot. Limit what it can reach, or stop using it until a fix ships, and follow the source advisory for updates.

Telegram allowlist authorization now requires numeric Telegram sender IDs only. @username allowlist principals are rejected. A security audit warning was added to flag legacy configs that still contain non-numeric Telegram allowlist entries. openclaw doctor --fix now attempts to resolve @username allowFrom entries to numeric IDs (best-effort; requires a Telegram bot token). e3b432e481a96b8fd41b91273818e514074e05c3 9e147f00b48e63e7be6964e0e2a97f2980854128 Thanks @vincentkoc for reporting.

Affected
PackageRegistryAffectedFixed in
clawdbotnpm<= 2026.1.24-3No fix yet
openclawnpm< 2026.2.142026.2.14

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