CVE-2026-41909: 
OpenClaw (formerly Moltbot or Clawdbot) vulnerability analysis and mitigation

CVE-2026-41909 is an improper authorization vulnerability in OpenClaw's paired-device pairing management that allows limited-scope sessions to enumerate and act on pairing requests belonging to other devices within the same gateway scope. It affects all OpenClaw (npm) versions before 2026.4.20 and was disclosed on April 23, 2026, with a patch released the same day. The CVE was assigned by VulnCheck and carries a CVSS v3.1 base score of 5.4 (Medium) and a CVSS v4.0 base score of 5.3 (Medium) (GitHub Advisory, Github Advisory).

The root cause is classified as CWE-863 (Incorrect Authorization) and CWE-284 (Improper Access Control): the pairing management subsystem failed to scope authorization checks to the calling device, instead exposing global gateway-level pairing state to any authenticated paired-device session (GitHub Advisory). An attacker with a valid paired-device token (low-privilege, network-accessible) could enumerate pending pairing requests across the gateway and approve or reject requests initiated by unrelated devices. The fix, committed in 5a12f30, restricts pairing list, approve, and reject actions to the caller's own device identity; admin and shared-secret operator sessions retain full visibility (Patch Commit).

Successful exploitation allows an authenticated paired-device session to enumerate other devices' pending pairing requests and approve or reject them without authorization, resulting in limited confidentiality and integrity impacts within the gateway scope. An attacker could modify device pairing configurations, potentially gaining access to resources or capabilities associated with another device's pairing relationship. Availability is not impacted, and the vulnerability does not affect systems outside the same gateway scope (GitHub Advisory, Github Advisory).

No public proof-of-concept exploit code exists and no in-the-wild exploitation has been observed as of the time of disclosure (Github Advisory). The EPSS score is approximately 0.025–0.034%, indicating a very low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, and no threat actor attribution has been reported.

1. Obtain paired-device credentials: Acquire a valid paired-device token for the target OpenClaw gateway (e.g., through a legitimately paired device or compromised device credentials).
2. Enumerate pairing requests: Using the paired-device session, send API requests to the pairing management endpoint to list all pending pairing requests at the gateway scope — requests that should only be visible to the owning device or an admin.
3. Identify target requests: Review the enumerated list to identify pairing requests belonging to other devices within the same gateway.
4. Approve or reject unrelated requests: Issue approve or reject actions against the identified pairing requests, effectively taking control of another device's pairing workflow and potentially gaining access to resources or capabilities associated with that device (GitHub Advisory, Patch Commit).

• Logs: Pairing management API requests (list, approve, reject) originating from a device token that does not match the device ID of the pairing request being acted upon; unusual volume of pairing enumeration calls from a single paired-device session.
• Application Behavior: Pairing requests approved or rejected without corresponding action from the owning device; unexpected device pairing state changes in gateway logs.
• Network: Repeated API calls to pairing management endpoints from a single authenticated session targeting multiple device pairing IDs in rapid succession.

Upgrade OpenClaw (npm) to version 2026.4.20 or later, which restricts pairing management actions (list, approve, reject) to the caller's own device identity (GitHub Advisory, Patch Commit). Until patching is complete, restrict network access to OpenClaw systems and limit paired-device access to trusted networks and users only. Monitor pairing request logs for unauthorized enumeration or approval activities as a compensating control.

The vulnerability was reported by researcher Hinotoi-agent and credited in the official advisory (GitHub Advisory). A brief community write-up was published on dev.to summarizing the issue and its fix. Overall community reaction has been minimal, consistent with the low severity rating and absence of active exploitation.