NewApp Monitoring is liveSign up free
AgentbeamBeta
AI agent vulnerability · OpenClaw

CVE-2026-28454: OpenClaw has a potential access-group authorization bypass if channel type lookup fails

criticalCVSS 4.0 9.1 · 3.1 9.8GHSA-fhvm-j76f-qmjv

OpenClaw up to 2026.1.30 accepts unauthenticated POST requests on its Telegram webhook endpoint when webhook mode is on and no webhook secret is set. An attacker who can reach the endpoint can forge Telegram updates, impersonate allowlisted senders and run privileged bot commands. Upgrade `openclaw` to 2026.2.1 or later.

Published Feb 17, 2026 · Updated Mar 6, 2026 · Analysis Nov 1, 2026

What an attacker can do

In Telegram webhook mode, OpenClaw trusts the update JSON in the request body. Without channels.telegram.webhookSecret, nothing proves the request came from Telegram. An attacker can post a crafted update with a spoofed message.from.id or chat.id. If that ID is on a sender allowlist or belongs to a paired user, the bot treats the message as theirs.

What the attacker gets depends on which commands and tools the bot has enabled, and on how far the webhook port is exposed. In a deployment where the agent runs tools, the forged sender can drive them. The scores are critical because the attack needs only network access, no credentials and no user action.

Only Telegram webhook mode without a secret is affected. Long-polling setups do not use the webhook endpoint. The advisory's title mentions an access-group check, but its text describes this webhook issue.

Who is affected

The openclaw npm package up to and including 2026.1.30, with Telegram webhook mode enabled (a webhookUrl configured) and no channels.telegram.webhookSecret. Check:

npm ls openclaw
openclaw --version

Then look in your config for channels.telegram.webhookUrl and channels.telegram.webhookSecret.

openclaw

Ecosystem
npm
Affected
< 2026.2.1
Fixed in
2026.2.1
Check
npm ls openclaw

How to fix it

Upgrade to 2026.2.1 or later:

npm install [email protected]

The main fix, commit ca92597e1f9593236ad86810b66633144b69314d, makes config validation require webhookSecret when webhookUrl is set. Supporting commits reject webhook startup when the secret is missing or empty, bind the listener to loopback by default, and bound request body size and time.

Workaround for older versions: set a strong channels.telegram.webhookSecret and make sure your reverse proxy forwards the X-Telegram-Bot-Api-Secret-Token header unchanged.

How to tell if you were hit

Check web server or proxy logs for POSTs to the Telegram webhook path from addresses outside Telegram's ranges, or without the X-Telegram-Bot-Api-Secret-Token header. Look through bot history for commands issued by allowlisted or paired users at times they were not active, and for tool actions that follow. Confirm whether a webhook secret has ever been configured.

Original advisory

From the GitHub Advisory Database (CC BY 4.0).

Summary

When Telegram webhook mode is enabled without a configured webhook secret, OpenClaw may accept unauthenticated HTTP POST requests at the Telegram webhook endpoint and trust attacker-controlled update JSON. This can allow forged Telegram updates that spoof message.from.id / chat.id, potentially bypassing sender allowlists and executing privileged bot commands.

Affected Packages / Versions

  • Package: openclaw (npm)
  • Affected: <= 2026.1.30
  • Patched: >= 2026.2.1

Impact

An attacker who can reach the webhook endpoint can forge Telegram updates and impersonate allowlisted/paired senders by spoofing fields in the webhook payload (for example message.from.id). Impact depends on enabled commands/tools and the deployment’s network exposure.

Mitigations / Workarounds

  • Configure a strong channels.telegram.webhookSecret and ensure your reverse proxy forwards the X-Telegram-Bot-Api-Secret-Token header unchanged.

Fix Commit(s)

  • ca92597e1f9593236ad86810b66633144b69314d (config validation: webhookUrl requires webhookSecret)

Defense-in-depth / supporting fixes:

  • 5643a934799dc523ec2ef18c007e1aa2c386b670 (default webhook listener bind host to loopback)
  • 3cbcba10cf30c2ffb898f0d8c7dfb929f15f8930 (bound webhook request body size/time)
  • 633fe8b9c17f02fcc68ecdb5ec212a5ace932f09 (runtime guard: reject webhook startup when secret is missing/empty)

Release Process Note

patched_versions is set to the first fixed release (2026.2.1).

Thanks @yueyueL for reporting.

Credited to simecek, stanislavfortaisle.

Questions

Does this affect OpenClaw bots that use long polling?

The advisory covers Telegram webhook mode without a secret. It does not describe the polling mode as affected.

Which version fixes CVE-2026-28454?

2026.2.1 is the first fixed release. Versions up to 2026.1.30 are affected.

Does setting the webhook secret fully protect me on older versions?

It is the advisory's listed mitigation, together with a proxy that forwards X-Telegram-Bot-Api-Secret-Token unchanged. Upgrading is still the proper fix.

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. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology

More OpenClaw vulnerabilities

All OpenClaw entries