AI agent vulnerability · OpenClaw

CVE-2026-28480: OpenClaw Telegram allowlist authorization accepted mutable usernames

mediumCVSS 4.0 6.9 · 3.1 5.9GHSA-mj5r-hh7j-4gxf

Summary Telegram allowlist authorization could match on @username (mutable/recyclable) instead of immutable numeric sender IDs. Impact 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.

Published Feb 18, 2026 · Updated Mar 6, 2026

Affected packages

openclaw

Ecosystem: npm
Affected: < 2026.2.14
Fixed in: 2026.2.14
Check: npm ls openclaw

clawdbot

Ecosystem: npm
Affected: <= 2026.1.24-3
Fixed in: No patched version yet
Check: npm ls clawdbot

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Summary

Telegram allowlist authorization could match on @username (mutable/recyclable) instead of immutable numeric sender IDs.

Impact

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.

Affected Packages / Versions

npm openclaw: <= 2026.2.13
npm clawdbot: <= 2026.1.24-3

Fix

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

Fix Commit(s)

e3b432e481a96b8fd41b91273818e514074e05c3
9e147f00b48e63e7be6964e0e2a97f2980854128

Thanks @vincentkoc for reporting.

Credited to vincentkoc.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More OpenClaw vulnerabilities

All OpenClaw entries