https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-04T04:52:57.962546+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2026-06158 bdu:2026-06158 2026-10-04T04:52:58.013517+00:00 bdu:2026-06158 https://cve.radiocsirt.org/vuln/brew-openclaw-cli-cve-2026-28480 BREW-openclaw-cli-CVE-2026-28480 — OpenClaw Telegram allowlist authorization accepted mutable usernames 2026-10-04T04:52:58.013552+00:00

Affected: Homebrew: openclaw-cli

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

 https://cve.radiocsirt.org/vuln/cnvd-2026-13544 cnvd-2026-13544 2026-10-04T04:52:58.013597+00:00 cnvd-2026-13544 https://cve.radiocsirt.org/vuln/euvd-2026-275144 EUVD-2026-275144 2026-10-04T04:52:58.013612+00:00 EUVD-2026-275144 https://cve.radiocsirt.org/vuln/fkie_cve-2026-28480 fkie_cve-2026-28480 2026-10-04T04:52:58.013623+00:00

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://cve.radiocsirt.org/vuln/ghsa-mj5r-hh7j-4gxf GHSA-mj5r-hh7j-4gxf — OpenClaw Telegram allowlist authorization accepted mutable usernames 2026-10-04T04:52:58.013645+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.

 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0424 WID-SEC-W-2026-0424 — OpenClaw: Mehrere Schwachstellen 2026-10-04T04:52:58.013676+00:00

Ein Angreifer kann diese Schwachstellen in OpenClaw ausnutzen, um beliebigen Programmcode auszuführen, sich erhöhte Berechtigungen zu verschaffen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen oder andere, nicht näher bezeichnete Angriffe durchzuführen.