https://db.gcve.eu/rss/recent/all/10 Most recent entries from all 2026-10-02T01:54:55.448754+00:00 Vulnerability-Lookup info@gcve.eu python-feedgen Contains only the most 10 recent entries. https://db.gcve.eu/vuln/cve-2026-28480 CVE-2026-28480 — OpenClaw < 2026.2.14 - Identity Spoofing via Mutable Username in Telegram Allowlist Authorization 2026-10-02T01:54:55.478676+00:00

Affected: OpenClaw

OpenClaw versions prior to 2026.2.14 contain an authorization bypass vulnerability where Telegram allowlist matching accepts mutable usernames instead of immutable numeric sender IDs. Attackers can spoof identity by obtaining recycled usernames to bypass allowlist restrictions and interact with bots as unauthorized senders.

 https://db.gcve.eu/vuln/ghsa-mj5r-hh7j-4gxf GHSA-mj5r-hh7j-4gxf — OpenClaw Telegram allowlist authorization accepted mutable usernames 2026-10-02T01:54:55.478790+00:00

Affected: npm: openclaw, npm: clawdbot

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