---
id: GHSA-w5ww-7chg-mxcq
title: 'OpenClaw: Telegram interactive callbacks could skip commands.allowFrom'
summary: 'OpenClaw: Telegram interactive callbacks could skip commands.allowFrom'
severity: high
cwe:
  - CWE-863
vendor: openclaw
product: openclaw
ecosystem: npm
affected:
  - openclaw <= 2026.5.5
patched:
  - openclaw 2026.5.6
published: '2026-07-02'
updated: '2026-07-02'
source: GHSA
sourceUrl: 'https://github.com/advisories/GHSA-w5ww-7chg-mxcq'
references:
  - url: >-
      https://github.com/openclaw/openclaw/security/advisories/GHSA-w5ww-7chg-mxcq
  - url: 'https://github.com/advisories/GHSA-w5ww-7chg-mxcq'
tags:
  - ghsa
  - npm
ingestedAt: '2026-07-02T17:40:39.302Z'
---

## Overview

### Summary

Telegram interactive callbacks could skip commands.allowFrom. In affected versions, a Telegram user able to invoke an affected callback could mark the callback as an authorized sender before applying `commands.allowFrom`.

This advisory is scoped to the named feature and configuration. It does not change OpenClaw's trusted-operator model: authenticated Gateway operators, installed plugins, and intentional local execution surfaces remain trusted unless a separate policy, approval, allowlist, sandbox, or auth boundary is crossed.

### Impact

When the affected feature is enabled and reachable, this could trigger command behavior outside the configured Telegram sender allowlist. Practical impact depends on the operator's configuration and whether lower-trust input can reach that path.

### Patched Versions

The first stable patched version is `2026.5.6`.

### Mitigations

restrict Telegram command callbacks to trusted chats until patched. As general hardening, keep channel and tool allowlists narrow, avoid sharing one Gateway between mutually untrusted users, and disable the affected feature when it is not needed.

## Affected packages

- `openclaw <= 2026.5.5`

## Remediation

Upgrade to a patched release:

- `openclaw 2026.5.6`