CVE-2026-32974: Openclaw Auth Bypass Vulnerability

CVE-2026-32974 Overview

OpenClaw before version 2026.3.12 contains an authentication bypass vulnerability in Feishu webhook mode. When only verificationToken is configured without encryptKey, the application accepts forged events, allowing unauthenticated network attackers to inject forged Feishu events and trigger downstream tool execution by reaching the webhook endpoint.

Critical Impact

Unauthenticated attackers can bypass authentication controls to inject malicious events into the webhook pipeline, potentially triggering arbitrary downstream tool execution and compromising system integrity.

Affected Products

• OpenClaw versions prior to 2026.3.12
• OpenClaw Node.js implementations with Feishu webhook mode enabled
• Deployments using verificationToken without encryptKey configuration

Discovery Timeline

• 2026-03-29 - CVE-2026-32974 published to NVD
• 2026-03-30 - Last updated in NVD database

Technical Details for CVE-2026-32974

Vulnerability Analysis

This authentication bypass vulnerability (CWE-347: Improper Verification of Cryptographic Signature) exists in OpenClaw's Feishu webhook integration. The flaw stems from an incomplete authentication implementation where the verificationToken alone provides insufficient security guarantees when the encryptKey parameter is not configured.

When webhook events are received, OpenClaw validates incoming requests using the verificationToken. However, this token-only verification approach is inherently vulnerable because the token can be intercepted or guessed, and without cryptographic signature validation provided by encryptKey, attackers can craft arbitrary events that pass authentication checks.

The vulnerability allows network-based attackers to reach the webhook endpoint and submit forged Feishu events that appear legitimate to the application. Once accepted, these malicious events propagate through the system and can trigger downstream tool execution, potentially leading to unauthorized command execution, data manipulation, or lateral movement within the affected infrastructure.

Root Cause

The root cause lies in the insufficient authentication mechanism when only verificationToken is used without encryptKey. The verificationToken parameter was designed as a basic validation mechanism but lacks the cryptographic integrity guarantees necessary to prevent event forgery. Without encryptKey, there is no cryptographic signature verification to ensure that incoming webhook events genuinely originate from Feishu's servers rather than an attacker.

Attack Vector

The attack vector is network-based and requires no authentication or user interaction. An attacker with network access to the webhook endpoint can craft HTTP requests that mimic legitimate Feishu webhook events. The attack flow involves:

1. Identifying the OpenClaw webhook endpoint exposed to the network
2. Crafting forged Feishu event payloads with valid structure
3. Submitting the forged events to the webhook endpoint
4. Bypassing authentication due to the missing encryptKey validation
5. Triggering downstream tool execution with attacker-controlled event data

The vulnerability is exploitable remotely without requiring prior authentication, making it particularly dangerous for internet-facing deployments. The attacker needs only to understand the Feishu event format and have network connectivity to the target webhook endpoint.

Detection Methods for CVE-2026-32974

Indicators of Compromise

• Unexpected or anomalous webhook requests to the OpenClaw Feishu endpoint from non-Feishu IP addresses
• Webhook events that trigger tool executions without corresponding legitimate Feishu user activity
• High volume of webhook requests from single source IPs not associated with Feishu infrastructure
• Downstream tool executions with suspicious or malformed parameters

Detection Strategies

• Monitor webhook endpoint access logs for requests originating from IP ranges outside Feishu's known infrastructure
• Implement network-level detection rules to identify forged webhook traffic patterns
• Configure application-level logging to capture all incoming webhook events and their source information
• Deploy web application firewall rules to validate webhook request signatures and headers

Monitoring Recommendations

• Enable detailed access logging for all OpenClaw webhook endpoints
• Set up alerts for failed or suspicious authentication attempts at the webhook layer
• Monitor downstream tool execution patterns for anomalies that may indicate injected events
• Correlate webhook activity with legitimate Feishu platform events where possible

How to Mitigate CVE-2026-32974

Immediate Actions Required

• Upgrade OpenClaw to version 2026.3.12 or later immediately
• Configure both verificationToken AND encryptKey parameters for Feishu webhook integration
• Restrict network access to webhook endpoints using firewall rules or network segmentation
• Review audit logs for any signs of exploitation prior to patching

Patch Information

The vulnerability has been addressed in OpenClaw version 2026.3.12. Organizations should upgrade to this version or later to remediate the authentication bypass. For detailed patch information, refer to the GitHub Security Advisory.

Additional technical analysis is available from the VulnCheck Advisory on OpenClaw.

Workarounds

• Configure encryptKey in addition to verificationToken to enable cryptographic signature validation
• Implement IP allowlisting to restrict webhook access to known Feishu IP ranges only
• Deploy a reverse proxy or web application firewall in front of the webhook endpoint to add additional validation layers
• Disable the Feishu webhook integration entirely if not actively required

# Configuration example - ensure both tokens are configured
# In your OpenClaw configuration file:
FEISHU_VERIFICATION_TOKEN=your_verification_token
FEISHU_ENCRYPT_KEY=your_encrypt_key

# Network restriction example using iptables
# Restrict webhook endpoint to Feishu IP ranges only
iptables -A INPUT -p tcp --dport 8080 -s feishu_ip_range -j ACCEPT
iptables -A INPUT -p tcp --dport 8080 -j DROP