OpenClaw Privilege Escalation via Telegram Configuration and Cron Persistence Settings
OpenClaw before 2026.3.28 contains a privilege escalation vulnerability that allows authenticated operators with write permissions to access and modify admin-class Telegram configuration and cron persistence settings via the send endpoint.
CVE search metadata
CVE search record: CVE-2026-41359. Severity: high. CVSS: 7.1. KEV: no. Product: OpenClaw. Brief: OpenClaw Privilege Escalation via Telegram Configuration and Cron Persistence Settings. Brief link: https://feed.craftedsignal.io/briefs/2026-04-24-openclaw-privesc/
Triage facts
Revision 2- Applicability
- OpenClaw
- Evidence
- Unknown
- Severity
- High
- Sources
- 4 public sources
- Freshness
- Revision 2Apr 24, 12:00 UTC
- Detection
- 2 rules
- Vulnerabilities
- 1 CVE
Revision history 1 entry · Revision 2
- Revision 2
Repaired a legacy canonical identity collision
Changed: slug
OpenClaw, in versions prior to 2026.3.28, is vulnerable to a privilege escalation. An authenticated operator with operator.write credentials can leverage this vulnerability to access sensitive administrative functions. Specifically, the flaw resides in the send endpoint where insufficient access controls allow unauthorized modification of Telegram configurations and cron persistence settings, which are typically restricted to admin-level users. Successful exploitation allows an attacker to gain elevated privileges and control critical system configurations. This can lead to persistent backdoor access or manipulation of the bot's behavior.
Attack Chain
- Attacker gains valid
operator.writecredentials through legitimate access or credential compromise. - Attacker authenticates to the OpenClaw instance.
- Attacker crafts a malicious request to the
/sendendpoint. - The crafted request targets the Telegram configuration settings, bypassing access controls.
- The attacker modifies sensitive Telegram configurations, potentially redirecting communications or impersonating the admin.
- The attacker manipulates the cron persistence settings to execute arbitrary code at scheduled intervals.
- The attacker establishes a persistent backdoor, maintaining unauthorized access to the system.
Impact
Successful exploitation of this vulnerability allows an attacker with limited operator.write privileges to gain administrative control over the OpenClaw instance. This could lead to unauthorized access to sensitive information, manipulation of the bot's functionality, or persistent backdoor access. The affected version is OpenClaw before 2026.3.28. There is no information about victim count or sectors targeted.
Recommendation
- Upgrade OpenClaw to version 2026.3.28 or later to patch CVE-2026-41359.
- Implement the Sigma rule
Detect OpenClaw Cron Persistence Modificationto monitor for unauthorized changes to cron jobs. - Implement the Sigma rule
Detect OpenClaw Telegram Configuration Modificationto monitor for unauthorized changes to telegram configurations.
Detection coverage 2
Detect OpenClaw Cron Persistence Modification
highDetects unauthorized modification of cron jobs, potentially indicating privilege escalation via CVE-2026-41359.
Detect OpenClaw Telegram Configuration Modification
highDetects unauthorized modification of telegram configuration, potentially indicating privilege escalation via CVE-2026-41359.
Detection queries are available on the platform. Get full rules →