CVE-2026-53856
Description
OpenClaw before 2026.4.24 has an insecure file permissions vulnerability in config recovery that exposes sensitive configuration data to local attackers on shared hosts.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
OpenClaw before 2026.4.24 has an insecure file permissions vulnerability in config recovery that exposes sensitive configuration data to local attackers on shared hosts.
Vulnerability
OpenClaw versions before 2026.4.24 contain an insecure file permissions vulnerability (CWE-732) in the config recovery feature. When configuration repair triggers the recovery path, the restored OpenClaw.json file is written with overly broad permissions, making it readable by other local users on the same host [1][2]. The affected feature is the config recovery mechanism, which is reachable when the operator initiates a configuration repair.
Exploitation
An attacker with local access to a shared host and low privileges (PR:L) can exploit this vulnerability. The attack vector is local (AV:L), requires no user interaction (UI:N), and has low attack complexity (AC:L). The attacker must wait for or trigger a config recovery event (e.g., via a repair operation). Once the recovery completes, the attacker can read the restored OpenClaw.json file due to its overly permissive file permissions [1][2].
Impact
Successful exploitation results in the disclosure of sensitive configuration data stored in OpenClaw.json. The confidentiality impact is high, while integrity and availability are not affected. The attacker gains read access to configuration details but does not achieve privilege escalation; the compromise is limited to information disclosure within the scope of the local host [1][2].
Mitigation
The vulnerability is fixed in OpenClaw version 2026.4.24 [1]. As a workaround, operators on shared hosts should manually check and correct the permissions of OpenClaw.json after any config recovery operation. Additional hardening measures include disabling the config recovery feature when not needed, keeping channel and tool allowlists narrow, and avoiding sharing a single Gateway instance between mutually untrusted users [1]. The vulnerability is not listed on the CISA Known Exploited Vulnerabilities (KEV) catalog as of the publication date.
AI Insight generated on Jun 16, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
2News mentions
0No linked articles in our index yet.