CVE-2026-32914
Insufficient Access Control in OpenClaw /config and /debug Handlers
Publication date: 2026-03-29
Last updated on: 2026-03-31
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| openclaw | openclaw | to 2026.3.12 (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
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized users with command authorization to access and modify privileged configuration settings that should be restricted to owners only. This unauthorized access to sensitive configuration data could lead to violations of data protection and security requirements mandated by common standards and regulations such as GDPR and HIPAA.
Specifically, the high confidentiality, integrity, and availability impacts indicated by the CVSS scores suggest that sensitive information could be exposed or altered, potentially resulting in non-compliance with regulations that require strict access controls and protection of sensitive data.
How can this vulnerability impact me? :
This vulnerability allows attackers with command authorization but without ownership privileges to access and modify privileged configuration and debugging settings.
The impact includes unauthorized disclosure of sensitive configuration data (high confidentiality impact), unauthorized modification of settings (high integrity impact), and potential disruption of component availability (high availability impact).
Because the attack vector is network-based and requires low privileges with no user interaction, it is relatively easy to exploit remotely.
Can you explain this vulnerability to me?
CVE-2026-32914 is an insufficient access control vulnerability in OpenClaw versions before 2026.3.12 affecting the /config and /debug command handlers.
These command handlers were intended to be accessible only by owners, but due to missing owner-level permission checks, users with command authorization who are not owners can access and modify privileged configuration settings.
This means attackers with command authorization can read or alter sensitive configuration data by exploiting the lack of proper authorization controls.
The vulnerability is classified under CWE-285 (Improper Authorization) and CWE-863 (Incorrect Authorization) and has a high severity with a CVSS score of 8.8.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves insufficient access control in the /config and /debug command handlers of OpenClaw versions prior to 2026.3.12. Detection would involve verifying whether non-owner users with command authorization can access or modify owner-only configuration settings.
To detect exploitation attempts or presence of this vulnerability, you can monitor network traffic or logs for unauthorized access to the /config and /debug endpoints by users who are not owners but have command authorization.
Specific commands to test this vulnerability would involve attempting to access or modify privileged configuration settings via the /config and /debug endpoints using a non-owner account that has command authorization.
For example, you might use curl or similar HTTP clients to send requests to these endpoints with credentials of a command-authorized non-owner user and observe if access is granted or modifications are accepted.
- curl -X GET https://<openclaw-server>/config -H "Authorization: Bearer <non-owner-command-token>"
- curl -X POST https://<openclaw-server>/debug -H "Authorization: Bearer <non-owner-command-token>" -d '{"someConfigChange": "value"}'
If these commands succeed in reading or modifying owner-only settings, the system is vulnerable.
What immediate steps should I take to mitigate this vulnerability?
The primary mitigation step is to upgrade OpenClaw to version 2026.3.12 or later, where the vulnerability has been fixed by enforcing proper owner-level permission checks on the /config and /debug command handlers.
Until the upgrade can be applied, restrict access to the /config and /debug endpoints to only trusted owner accounts and avoid granting command authorization to non-owner users.
Additionally, monitor logs and network traffic for any unauthorized access attempts to these endpoints and revoke or limit command authorization privileges where possible.