N/A

CVSS Score

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

GHSA-767m-xrhc-fxm7

GHSA-767m-xrhc-fxm7: OpenClaw: Gateway operator.write Can Reach Admin-Class Telegram Config and Cron Persistence via send

Summary

Gateway operator.write Can Reach Admin-Class Telegram Config and Cron Persistence via send

Current Maintainer Triage

Status: narrow
Normalized severity: medium
Assessment: Real shipped operator.write to admin-class Telegram config or cron persistence bug, but it is an authenticated sink-specific escalation and high is too high given the narrower scope.

Affected Packages / Versions

Package: openclaw (npm)
Latest published npm version: 2026.3.31
Vulnerable version range: <=2026.3.24
Patched versions: >= 2026.3.28
First stable tag containing the fix: v2026.3.28

Fix Commit(s)

b7d70ade3b9900dbe97bd73be9c02e924ff3c986 — 2026-03-25T12:12:09-06:00

Release Process Note

The fix is already present in released version 2026.3.28.
This draft looks ready for final maintainer disposition or publication, not additional code-fix work.

Thanks @zpbrent for reporting.

(GitHub Advisory)

Miggo Vulnerability Database

→

GHSA-767m-xrhc-fxm7

GHSA-767m-xrhc-fxm7:

N/A

CVSS Score

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
openclaw	npm	<= 2026.3.24	2026.3.28

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability is a privilege escalation in the 'openclaw' application, where a user with 'operator.write' permissions could perform actions that should be restricted to 'operator.admin'. Specifically, when sending a message or a poll to a Telegram channel using a non-numeric alias (e.g., '@channelname'), the application resolves this alias to a numeric chat ID. It then attempts to persist this resolved ID back into the main configuration file and any associated cron jobs. This writeback operation is a privileged action.

The root cause of the vulnerability was the failure to check the user's permissions before performing this writeback. The gateway methods sendHandlers.send and sendHandlers.poll were the entry points for this vulnerable workflow. They accepted requests from users with operator.write scope but did not propagate the user's scope information down the call chain.

The function maybePersistResolvedTelegramTarget in extensions/telegram/src/target-writeback.ts was the function that performed the unsafe write operation without any permission checks.

The patch addresses this by passing the client's security scopes (as gatewayClientScopes) from the initial gateway request all the way down to maybePersistResolvedTelegramTarget. This function now includes a check to ensure the operator.admin scope is present before attempting to modify any configuration or cron jobs, effectively closing the privilege escalation vector.

Vulnerable functions

sendHandlers.send

src/gateway/server-methods/send.ts

This is the gateway API endpoint for sending messages. Before the patch, it did not check or propagate the client's security scopes. This allowed a user with only 'operator.write' permission to trigger a privileged configuration writeback operation (persisting resolved Telegram chat IDs to config and cron jobs) that should have been restricted to users with 'operator.admin' permission.

sendHandlers.poll

src/gateway/server-methods/send.ts

This is the gateway API endpoint for creating polls. Similar to the 'send' method, it did not check or propagate the client's security scopes. This allowed a user with only 'operator.write' permission to trigger a privileged configuration writeback operation (persisting resolved Telegram chat IDs to config and cron jobs) that should have been restricted to users with 'operator.admin' permission.

maybePersistResolvedTelegramTarget

extensions/telegram/src/target-writeback.ts

This function is responsible for persisting resolved Telegram chat IDs to the main configuration file and cron jobs. The vulnerability lies in the absence of a permission check before performing this sensitive write operation. The patch adds a check to ensure the caller has the 'operator.admin' scope, thus fixing the privilege escalation vulnerability. Before the fix, any process that could trigger this function could modify system configuration.

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.