CVE-2026-62205: Openclaw Auth Bypass Vulnerability

CVE-2026-62205 Overview

CVE-2026-62205 is a missing-authorization vulnerability [CWE-862] affecting OpenClaw versions 2026.4.12-beta.1 through versions before 2026.6.6. The flaw resides in the Microsoft Teams message actions feature. When the feature is enabled and reachable, a lower-trust caller or a configured input path can invoke actions that should require stronger authorization or policy checks.

The vulnerability is fixed in OpenClaw 2026.6.6. Practical impact depends on operator configuration and whether lower-trust input can reach the affected code path.

Critical Impact
Attackers with low privileges can bypass authorization checks in the MS Teams message actions feature to perform actions that should require elevated permissions or policy validation.

Affected Products

OpenClaw 2026.4.12-beta.1 through versions before 2026.6.6
OpenClaw deployments running on Node.js
Instances with the MS Teams message actions feature enabled and reachable

Discovery Timeline

2026-07-17 - CVE-2026-62205 published to the National Vulnerability Database (NVD)
2026-07-21 - Last updated in NVD database

Technical Details for CVE-2026-62205

Vulnerability Analysis

The vulnerability is a missing authorization check [CWE-862] within the MS Teams message actions feature in OpenClaw. The affected code path processes actions triggered by Teams messages without verifying that the caller holds the authorization level required to perform those actions.

Exploitation requires network access and low-level privileges. An attacker submits input to the message actions handler that reaches the privileged action logic. The handler executes the requested action without performing the policy check that gates higher-trust operations.

Impact centers on integrity. The Common Vulnerability Scoring System (CVSS) 4.0 vector records high integrity impact (VI:H) with low availability impact (VA:L) and no confidentiality impact (VC:N). Whether the flaw is reachable depends on the operator's configuration and how lower-trust input flows into the feature.

Root Cause

The root cause is a missing authorization check in the MS Teams message actions handler. Code that performs sensitive actions does not verify caller trust level or apply the policy that should gate the action. The result is a broken access control condition where authenticated but low-privilege callers can trigger privileged behavior.

Attack Vector

The attack vector is network-based (AV:N). An authenticated caller with low privileges (PR:L) submits crafted input to the MS Teams message actions path. Attack complexity is low, but the CVSS 4.0 vector marks attack requirements as present (AT:P) — the target operator must have the feature enabled and a reachable input path configured. No user interaction is required.

For technical details, see the GitHub Security Advisory GHSA-p5xh-frrh-cmgj and the VulnCheck Advisory on OpenClaw.

Detection Methods for CVE-2026-62205

Indicators of Compromise

Unexpected invocations of MS Teams message actions from accounts with limited privileges
Application log entries showing actions executed without a preceding authorization decision
Requests to the message actions endpoint originating from unusual source addresses or automated clients

Detection Strategies

Review application logs for successful message action executions initiated by low-trust principals
Compare the acting principal against the policy that should have gated the action and flag divergences
Alert on volume spikes or off-hours activity against the MS Teams message actions handler

Monitoring Recommendations

Ingest OpenClaw application and access logs into a centralized SIEM or data lake for correlation
Track the running OpenClaw version across all deployments and alert when versions match the vulnerable range
Monitor identity provider events tied to accounts that interact with the MS Teams message actions feature

How to Mitigate CVE-2026-62205

Immediate Actions Required

Upgrade OpenClaw to version 2026.6.6 or later, which contains the fix
Inventory all OpenClaw instances and confirm whether the MS Teams message actions feature is enabled
Audit recent application logs for actions performed by low-privilege principals against the affected feature

Patch Information

The issue is fixed in OpenClaw 2026.6.6. Upgrade guidance and patch metadata are published in the GitHub Security Advisory GHSA-p5xh-frrh-cmgj. Operators running any release from 2026.4.12-beta.1 up to but not including 2026.6.6 should update immediately.

Workarounds

Disable the MS Teams message actions feature until the upgrade to 2026.6.6 is complete
Restrict network reachability of the message actions endpoint to trusted callers and internal networks
Enforce stricter authorization at an upstream proxy or gateway for requests targeting the affected path

bash

# Upgrade OpenClaw to the fixed release
npm install openclaw@2026.6.6

# Verify the installed version
npm ls openclaw