CVEReports
CVEReports

Automated vulnerability intelligence platform. Comprehensive reports for high-severity CVEs generated by AI.

Product

  • Home
  • Sitemap
  • RSS Feed

Company

  • About
  • Contact
  • Privacy Policy
  • Terms of Service

© 2026 CVEReports. All rights reserved.

Made with love by Amit Schendel & Alon Barad



CVE-2026-53854

CVE-2026-53854: Privilege Escalation via Wildcard Authorization Inheritance in OpenClaw

Amit Schendel
Amit Schendel
Senior Security Researcher

Jun 19, 2026·5 min read·57 visits

Executive Summary (TL;DR)

A privilege escalation vulnerability in OpenClaw allows low-privilege internal/webchat senders to inherit wildcard administrative permissions, leading to unauthorized owner-level command execution.

CVE-2026-53854 is an authorization bypass vulnerability in OpenClaw, an open-source WhatsApp gateway CLI and Pi RPC agent. The flaw exists in the command authentication flow where low-privilege actors communicating via internal or webchat interfaces inherit global wildcard authorization states across channel boundaries. This cross-channel inheritance allows unauthorized command execution with administrative privileges.

Vulnerability Overview

OpenClaw is a WhatsApp gateway CLI built on the Baileys web API with an integrated Pi RPC agent. The system coordinates message routing across multiple channels, including WhatsApp chats, Slack, Discord, internal debug interfaces, and local webchat configurations.

To secure sensitive administration functions, OpenClaw implements an operator-trust model. This mechanism differentiates between operators with full administrative capabilities and channel-scoped users who are restricted to limited, non-administrative commands.

Authorization for administrative commands is governed by the ownerAllowFrom setting, which defines authorized identifiers for owner-level actions. A weakness exists in how the gateway evaluates authorization states when commands are received over internal or webchat communication paths, resulting in incorrect authorization enforcement.

Root Cause Analysis

The root cause of CVE-2026-53854 is classified under CWE-863 (Incorrect Authorization). The vulnerability occurs within the command-routing controller during authorization checks on incoming messages.

When evaluating permissions, the controller checks whether the channel configuration has wildcard privileges enabled, designated by a wildcard value (such as *) within the ownerAllowFrom setting. If a high-privilege channel utilizes this wildcard configuration, the state context of the controller is flagged as authorized.

Due to insufficient boundary isolation, this authorization state is not cleared before subsequent evaluations of other channels. When a lower-privileged user sends a request via an internal or webchat communication path, the authorization engine references the uncleared, active state. This state inheritance allows the lower-privilege connection to execute restricted commands with administrative permissions.

Code-Level Flow Analysis

The following code block demonstrates a conceptual model of the vulnerable context-handling loop, where the authorization state is retained across requests:

// Vulnerable Controller State Evaluation
class CommandController {
  constructor() {
    this.authState = {}; // Shared context variable
  }
 
  evaluateAuthorization(request) {
    // If the channel configuration specifies a wildcard, the state is flag-marked
    if (request.channelConfig.ownerAllowFrom === '*') {
      this.authState.isOwnerAllowed = true;
    }
    // BUG: If isOwnerAllowed is true from a previous evaluation, 
    // it is never reset to false for subsequent channels that do not have wildcards.
    return this.authState.isOwnerAllowed;
  }
}

To resolve this vulnerability, the context validation must be explicitly restricted to the current request scope. Re-initializing the context on every evaluation cycle prevents previous authorization outcomes from leaking into new sessions:

// Patched Controller State Evaluation
class CommandController {
  evaluateAuthorization(request) {
    // Fix: Scope state evaluation locally to prevent bleed across boundaries
    let isOwnerAllowed = false;
 
    if (request.channelConfig.ownerAllowFrom === '*') {
      isOwnerAllowed = true;
    } else {
      // Perform explicit credential and channel verification
      isOwnerAllowed = this.verifySenderIdentity(request.sender, request.channelConfig.ownerAllowFrom);
    }
    return isOwnerAllowed;
  }
}

Threat Modeling & Exploitation Steps

Exploiting CVE-2026-53854 requires a low-privilege attacker to have network access to an active, exposed OpenClaw gateway instance. The target gateway must also have at least one channel configured with a wildcard administrative setting.

The attacker initiates a connection using the webchat path or internal command interface. By sending a request that triggers the evaluation routine, the attacker forces the controller to process authorization against the active state context.

Because the shared context contains the wildcard flag inherited from the high-privilege configuration, the check passes. The command is successfully routed and executed with full operator-style rights, bypassing standard access controls.

Impact Assessment and Risk Matrix

The potential consequences of successful exploitation include complete compromise of gateway integrity. An attacker can execute arbitrary commands directly on the host system or through the connected Pi RPC agent.

Since OpenClaw controls the message transmission lifecycle, unauthorized administrative commands allow attackers to inject malicious messages, manipulate session databases, and intercept incoming communications. Additionally, the RPC interface could be used to interact with hardware peripherals managed by the host system.

The vulnerability is scored with a Medium severity rating of 6.0 on the CVSS scale. This score reflects the requirement for low-level initial privileges (PR:L) and specific configuration preconditions (AT:P), balancing the overall risk despite the high integrity impact.

Defensive Engineering & Remediation

The primary defense against this vulnerability is updating OpenClaw to version 2026.4.25 or later. This release enforces strict context boundary checks, preventing the sharing of authorization variables between channels.

If upgrading is not immediately possible, operators should eliminate wildcard operators in configuration files. Explicit allowlists should replace any entries containing wildcards in the ownerAllowFrom parameters.

Administrators must also implement network access control lists to isolate the webchat and internal interfaces. Restricting access to trusted administrative hosts or local loopback interfaces reduces the overall remote attack surface.

Technical Appendix

CVSS Score
6.0/ 10
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Affected Systems

OpenClaw
AttributeDetail
CWE IDCWE-863
Attack VectorNetwork
CVSS Score6.0
EPSS Score0.00247
Exploit StatusNone
CISA KEV StatusNot Listed
CWE-863
Incorrect Authorization

Vulnerability Timeline

CVE Published and assigned by VulnCheck
2026-06-16
GitHub Security Advisory published to GitHub Advisory Database
2026-06-18

References & Sources

  • [1]GitHub Security Advisory GHSA-4hpg-mp64-x7xq

More Reports

•15 minutes ago•CVE-2026-114147
7.5

CVE-2026-114147: Denial of Service via Memory Leak in ASP.NET Core SignalR Redis Backplane

CVE-2026-114147 is a high-severity Denial of Service (DoS) vulnerability affecting ASP.NET Core and specifically the Microsoft.AspNetCore.SignalR.StackExchangeRedis scale-out provider across .NET 8.0, 9.0, 10.0, and 11.0 preview releases. The vulnerability originates from a string comparison mismatch between internal per-connection group collections and the centralized Redis channel subscription registry, compounded by a race condition during connection teardown. Remote unauthenticated attackers can exploit this flaw to leave orphaned connection contexts and active Redis pub/sub listeners pinned in memory, leading to unbounded memory exhaustion and application process termination.

Amit Schendel
Amit Schendel
0 views•10 min read
•about 1 hour ago•CVE-2026-114156
6.5

CVE-2026-114156: Path Equivalence Security Feature Bypass in Microsoft ASP.NET Core

CVE-2026-114156 is an improper resolution of path equivalence vulnerability (CWE-41) in Microsoft ASP.NET Core affecting .NET 11.0 preview releases and Microsoft Visual Studio 2026. The vulnerability stems from a discrepancy between how path prefix validation helpers (such as PathString.StartsWithSegments) and downstream routing mechanisms handle alternate path separators and percent-encoded characters. An unauthenticated remote attacker can exploit this mismatch over the network to bypass path-based authorization middleware and access restricted endpoints.

Amit Schendel
Amit Schendel
4 views•8 min read
•about 2 hours ago•CVE-2026-114157
7.5

CVE-2026-114157: Local Privilege Escalation via Race Condition in ASP.NET Core Kestrel Named Pipes Transport

CVE-2026-114157 is a high-severity local privilege escalation and security feature bypass vulnerability affecting ASP.NET Core on Microsoft Windows. The flaw resides in the Kestrel web server's Named Pipes transport layer (Microsoft.AspNetCore.Server.Kestrel.Transport.NamedPipes) and stems from a race condition (CWE-362) during broken pipe error recovery. When an active connection throws an IOException during handshake acceptance, the connection listener previously disposed of the broken NamedPipeServerStream instance before acquiring a replacement stream from its internal pool. This sequence created a momentary window where zero server instances of the named pipe existed in the Windows Named Pipe File System (NPFS). A local, low-privileged attacker can exploit this timing window to create a named pipe with the identical name and a permissive Discretionary Access Control List (DACL), hijacking subsequent inter-process communications and escalating privileges across security boundaries.

Amit Schendel
Amit Schendel
6 views•11 min read
•about 3 hours ago•CVE-2026-124194
6.5

CVE-2026-124194: Forced Authentication and NetNTLMv2 Credential Leakage in Microsoft Office Outlook

CVE-2026-124194 is a forced authentication and spoofing vulnerability in Microsoft Office Outlook caused by a missing user interface warning before dereferencing remote network paths (CWE-356). By embedding an attacker-controlled Universal Naming Convention (UNC) path within MAPI message properties such as PidLidReminderFileParameter, an unauthenticated remote attacker can force a victim's system to initiate an outbound SMB or WebDAV connection upon opening or previewing a crafted message. This automatic authentication handshake leaks the user's NetNTLMv2 hash, enabling offline password cracking or real-time NTLM relay attacks. The vulnerability was exploited in the wild as a zero-day prior to its remediation in Microsoft's November 2026 Patch Tuesday updates and is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.

Alon Barad
Alon Barad
14 views•10 min read
•about 3 hours ago•CVE-2026-114154
7.5

CVE-2026-114154: Denial of Service in ASP.NET Core HttpSys Request Header Processing

CVE-2026-114154 is a high-severity Denial of Service (DoS) and uncontrolled resource consumption vulnerability in the Microsoft.AspNetCore.Server.HttpSys component of ASP.NET Core. When processing an HTTP request that simultaneously contains a chunked Transfer-Encoding header, a Content-Length header, and an explicit X-Content-Length header, the server throws an unhandled ArgumentException during header normalization. In certain versions, subsequent exception handling attempts to dereference a disposed native request context, aborting error response dispatch and leaking unmanaged HTTP.sys request structures.

Amit Schendel
Amit Schendel
4 views•9 min read
•about 4 hours ago•CVE-2026-120778
7.3

CVE-2026-120778: Local Elevation of Privilege via Insecure Temporary Directory Handling and MSBuild Response File Hijacking in Microsoft .NET Aspire CLI

A local elevation of privilege vulnerability exists in the Microsoft .NET Aspire CLI (`Aspire.Cli`) versions 13.5.4 prior to 13.6.5. When executing SDK management commands (`aspire sdk generate`, `aspire sdk dump`, and `aspire sdk export`), the CLI creates temporary project directories inside the shared operating system temporary folder (such as `/tmp` on Unix-like systems) without restricting directory permissions or disabling MSBuild automatic response file resolution. A local, low-privileged attacker on a multi-user system can place a crafted `Directory.Build.rsp` file in the shared temporary directory hierarchy. When a victim user executes an affected Aspire CLI command, MSBuild traverses upward, ingests the attacker-controlled response file, and executes arbitrary commands in the security context of the victim user.

Alon Barad
Alon Barad
4 views•10 min read