Telegram allowlist authorization could match on @username (mutable/recyclable) instead of immutable numeric sender IDs.
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.
openclaw: <= 2026.2.13clawdbot: <= 2026.1.24-3Telegram 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).
Thanks @vincentkoc for reporting.
{
"github_reviewed": true,
"github_reviewed_at": "2026-02-18T00:54:32Z",
"cwe_ids": [
"CWE-284",
"CWE-290"
],
"severity": "MODERATE",
"nvd_published_at": "2026-03-05T22:16:22Z"
}