---
title: "CVE-2026-28454: OpenClaw has a potential access-group authorization bypass if channel type lookup fails"
url: https://erroneo.us/security/cve/CVE-2026-28454/
description: "CVE-2026-28454 (openclaw (npm)): OpenClaw versions prior to 2026.2.2 fail to validate webhook secrets in Telegram webhook mode (must be enabled), allowing…"
type: vulnerability-record
section: "Security Digest"
date_published: 2026-03-05
date_modified: 2026-03-09
publisher: erroneo.us
author: erroneo.us Security Desk
cve: "CVE-2026-28454"
kev: false
cvss: 8.2
epss: 0.00407
license: All rights reserved. Quote with attribution and a link.
---

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

**Signal:** Normal patch cycle. No exploitation signal; fix it in your next routine update if you are affected. (Computed from CISA KEV, EPSS and CVSS; not an editorial verdict.)

## Should you act?

- No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
- EPSS 0.4% , percentile 34: FIRST’s model estimates a 0.4% chance of exploitation activity in the next 30 days, higher than 34% of all scored CVEs (low). EPSS is a probability, not a verdict.
- Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
- Only applies if your dependency tree includes openclaw (npm) < 2026.2.1, fixed in 2026.2.1 . Check your lockfile, including transitive dependencies.

## What it is

OpenClaw versions prior to 2026.2.2 fail to validate webhook secrets in Telegram webhook mode (must be enabled), allowing unauthenticated HTTP POST requests to the webhook endpoint that trust attacker-controlled JSON payloads. Remote attackers can forge Telegram updates by spoofing message.from.id and chat.id fields to bypass sender allowlists and execute privileged bot commands.

## Affected packages

- npm `openclaw` < 2026.2.1 → fixed: 2026.2.1

## Affected products (CVE record)

- OpenClaw OpenClaw: < 2026.2.2

## Severity

- VulnCheck CVSS 4.0: 8.2 `CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`
- VulnCheck CVSS 3.1: 7.5 `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`
- GitHub CVSS 4.0: 9.1 `CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`

## Exploitation

- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation none , automatable yes , technical impact partial .
- FIRST EPSS (model of 2026-10-21): 0.41% probability of exploitation activity in the next 30 days; percentile 34.

## Sources

- [GitHub Security Advisory (GHSA-fhvm-j76f-qmjv)](https://github.com/openclaw/openclaw/security/advisories/GHSA-fhvm-j76f-qmjv)
- [Patch Commit](https://github.com/openclaw/openclaw/commit/ca92597e1f9593236ad86810b66633144b69314d)
- [Hardening Commit #1](https://github.com/openclaw/openclaw/commit/5643a934799dc523ec2ef18c007e1aa2c386b670)
- [Hardening Commit #2](https://github.com/openclaw/openclaw/commit/3cbcba10cf30c2ffb898f0d8c7dfb929f15f8930)
- [Hardening Commit #3](https://github.com/openclaw/openclaw/commit/633fe8b9c17f02fcc68ecdb5ec212a5ace932f09)
- [GitHub Advisory GHSA-fhvm-j76f-qmjv](https://github.com/advisories/GHSA-fhvm-j76f-qmjv)
- [CVE.org record CVE-2026-28454](https://www.cve.org/CVERecord?id=CVE-2026-28454)
- [NVD entry CVE-2026-28454](https://nvd.nist.gov/vuln/detail/CVE-2026-28454)
- [VulnCheck Advisory: OpenClaw < 2026.2.2 - Authorization Bypass via Unauthenticated Telegram Webhook](https://www.vulncheck.com/advisories/openclaw-authorization-bypass-via-unauthenticated-telegram-webhook)
- [github.com](https://github.com/openclaw/openclaw/releases/tag/v2026.2.1)

---
Source page: https://erroneo.us/security/cve/CVE-2026-28454/ · Security Digest: https://erroneo.us/security/ · More: https://erroneo.us/llms.txt