Skip to main content
CVE Vulnerability Database
Vulnerability Database/CVE-2026-62221

CVE-2026-62221: Openclaw Authorization Bypass Vulnerability

CVE-2026-62221 is an authorization bypass flaw in Openclaw's ClickClack allowFrom feature that lets attackers execute unauthorized commands. This article covers technical details, affected versions, impact, and mitigation.

Published:

CVE-2026-62221 Overview

CVE-2026-62221 is an incorrect authorization vulnerability [CWE-863] in OpenClaw, a Node.js package published by the openclaw project. The flaw resides in the ClickClack allowFrom feature and affects versions 2026.5.12 through releases prior to 2026.5.26. When the feature is enabled and reachable over the network, a lower-trust caller or configured input path can execute or persist actions beyond the caller's intended authorization, including running non-allowlisted commands. The issue is tracked in a GitHub Security Advisory and a VulnCheck Advisory: OpenClaw Bypass.

Critical Impact

Authenticated low-privilege callers can bypass the allowFrom allowlist to execute unauthorized commands within OpenClaw deployments.

Affected Products

  • OpenClaw openclaw (Node.js package) versions 2026.5.12 through pre-2026.5.26
  • Deployments where the ClickClack allowFrom feature is enabled
  • Applications exposing OpenClaw over the network to lower-trust callers

Discovery Timeline

  • 2026-07-17 - CVE-2026-62221 published to NVD
  • 2026-07-21 - Last updated in NVD database

Technical Details for CVE-2026-62221

Vulnerability Analysis

The vulnerability is an incorrect authorization weakness [CWE-863] in the ClickClack component's allowFrom feature. The allowFrom mechanism is intended to restrict which callers or configured input paths can trigger sensitive actions. Because the authorization check does not correctly enforce this allowlist, a lower-trust caller can invoke actions that should be rejected. Successful abuse allows execution or persistence of operations outside the caller's intended authorization scope, including running commands not present in the allowlist.

The attack surface is network-reachable and requires low privileges, according to the CVSS 4.0 vector. Exploitation depends on an attack requirement (AT:P) — the feature must be enabled and reachable — which limits opportunistic abuse. Confidentiality and integrity impact are limited to the vulnerable component, and availability is not affected. EPSS data reports a low probability of near-term exploitation.

Root Cause

The root cause is an inconsistent authorization decision inside the ClickClack allowFrom code path. The check evaluates caller identity or input origin but fails to correctly reconcile that value against the configured allowlist. As a result, non-allowlisted commands pass the authorization gate and reach downstream execution logic.

Attack Vector

An attacker sends a crafted request to a reachable OpenClaw endpoint where ClickClack allowFrom is enabled. With low-privilege credentials or through a configured input path that the attacker can influence, the attacker submits a command outside the allowlist. The flawed authorization check accepts the request, and OpenClaw executes or persists the action. No verified public proof-of-concept code has been published; refer to the VulnCheck Advisory: OpenClaw Bypass for technical details.

Detection Methods for CVE-2026-62221

Indicators of Compromise

  • Execution of commands by OpenClaw that are not present in the configured allowFrom allowlist.
  • Unexpected process spawns or persistence artifacts originating from the Node.js process hosting openclaw.
  • Requests to ClickClack endpoints from low-privilege accounts or unexpected source paths immediately preceding privileged actions.

Detection Strategies

  • Inventory Node.js dependencies and flag installations of openclaw at versions 2026.5.12 through pre-2026.5.26.
  • Correlate application logs where ClickClack allowFrom decisions are recorded and alert when allowed commands do not match the static allowlist configuration.
  • Baseline the set of commands OpenClaw legitimately executes, then alert on deviations at the process-execution layer.

Monitoring Recommendations

  • Monitor child processes spawned by the OpenClaw Node.js runtime for unexpected binaries or arguments.
  • Log and review every authorization decision returned by allowFrom with the caller identity and command string.
  • Track outbound activity from hosts running OpenClaw for signs of secondary command execution or persistence.

How to Mitigate CVE-2026-62221

Immediate Actions Required

  • Upgrade openclaw to version 2026.5.26 or later across all affected Node.js applications.
  • If upgrading is not immediately feasible, disable the ClickClack allowFrom feature until the patched release is deployed.
  • Restrict network reachability to OpenClaw endpoints so only trusted callers can reach the vulnerable feature.

Patch Information

OpenClaw addresses the incorrect authorization issue in version 2026.5.26. Consult the GitHub Security Advisory for fix details and version guidance. Update through the standard npm/yarn dependency workflow and rebuild affected services.

Workarounds

  • Disable the ClickClack allowFrom feature in configuration where operationally acceptable.
  • Enforce authentication and network segmentation so that only high-trust callers can reach OpenClaw endpoints.
  • Reduce the allowlist to the minimum set of commands required, limiting the blast radius if the check is bypassed.
bash
# Upgrade the vulnerable package to the fixed release
npm install openclaw@2026.5.26

# Verify installed version
npm ls openclaw

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Default Legacy - Prefooter | Experience the World’s Most Advanced Cybersecurity Platform

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.