CVE-2026-42429
Privilege Escalation in OpenClaw Gateway Plugin HTTP Auth
Publication date: 2026-04-28
Last updated on: 2026-04-30
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| openclaw | openclaw | to 2026.4.8 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-863 | The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-42429 is a privilege escalation vulnerability in OpenClaw versions before 2026.4.8. It occurs in the gateway plugin's HTTP authentication mechanism, where requests that should only have operator.read permissions are incorrectly granted operator.write permissions at runtime.
This means an attacker who can send read-scoped requests through the gateway authentication route can gain unauthorized write access to runtime operations, effectively escalating their privileges beyond what they should have.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
The vulnerability in OpenClaw before version 2026.4.8 involves improper authorization in the gateway plugin HTTP authentication mechanism, where operator.read scoped requests are escalated to operator.write permissions. Detection would involve monitoring or testing HTTP requests sent through the gateway authentication route to identify if read-scoped requests are improperly granted write access.
Since the vulnerability is related to HTTP authentication and permission escalation, detection could include sending crafted HTTP requests with operator.read scope and verifying if write operations are allowed unexpectedly.
No specific detection commands or tools are provided in the available resources. However, a general approach might involve using tools like curl or HTTP clients to send read-scoped requests to the gateway plugin endpoints and checking the response or behavior for unauthorized write access.
- Example command to test the vulnerability (conceptual):
- curl -X POST -H "Authorization: Bearer <token_with_operator.read_scope>" https://<openclaw_gateway_endpoint>/runtime/write-operation
If the request succeeds in performing a write operation despite the token only having read scope, the system is vulnerable.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify how CVE-2026-42429 affects compliance with common standards and regulations such as GDPR or HIPAA.
How can this vulnerability impact me? :
The vulnerability allows an attacker with read-level access to escalate their privileges to write-level access within the OpenClaw system. This unauthorized write access can lead to manipulation or alteration of runtime operations, potentially compromising system integrity and security.
What immediate steps should I take to mitigate this vulnerability?
To mitigate the vulnerability CVE-2026-42429, you should upgrade OpenClaw to version 2026.4.8 or later, where the issue has been fixed.
The vulnerability arises from incorrect authorization in the gateway plugin HTTP authentication mechanism, so applying the official patch or update is the recommended immediate step.