Is there a public PoC exploit available for CVE-2026-53856?

Yes, a public proof-of-concept exploit is available for CVE-2026-53856. Prioritise patching immediately. EPSS: 0.1%.

Is there a patch available for CVE-2026-53856?

Yes, a patch is available for CVE-2026-53856. Update the affected software to the latest version immediately.

OpenClaw CVE-2026-53856

Q: What is the CVSS score of CVE-2026-53856?

CVE-2026-53856 has a CVSS 4.0 base score of 5.7 (Medium). CVSS vector: CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.1%.

EUVD-2026-37158 MEDIUM

Incorrect Permission Assignment for Critical Resource (CWE-732)

2026-06-16 VulnCheck

GHSA-rwp6-7w3q-75fq

GHSA-vqj9-vhg4-27mg

Information Disclosure Openclaw

5.7

CVSS 4.0 · Vendor: VulnCheck

Severity by source

Vendor (VulnCheck) PRIMARY

5.7 MEDIUM

CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

5.5 MEDIUM

Local vector and low-privilege requirement reflect shared-host prerequisites; high confidentiality impact for config file exposure; no integrity or availability impact applies.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Patch available

Jun 16, 2026 - 20:02 EUVD

Analysis Generated

Jun 16, 2026 - 19:02 vuln.today

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

1 npm packages depend on openclaw (1 direct, 0 indirect)

Ecosystem-wide dependent count for version 2026.4.23.

DescriptionCVE.org

OpenClaw before 2026.4.24 contains an insecure file permissions vulnerability in config recovery that restores OpenClaw.json with overly broad permissions. Local attackers on shared hosts can read sensitive configuration data by exploiting the recovery path to access the restored config file.

AnalysisAI

OpenClaw before 2026.4.24 exposes sensitive configuration data to other local users on shared hosts due to insecure file permissions set during the config recovery process. When recovery restores OpenClaw.json, the resulting file is created with overly broad permissions, allowing any low-privileged local user to read its contents. No public exploit has been identified at time of analysis, but exploitation requires only a low-privilege local account and a shared-host environment where the recovery path has been exercised.

Technical ContextAI

The root cause is CWE-732 (Incorrect Permission Assignment for Critical Resource). The config recovery mechanism in OpenClaw reconstructs OpenClaw.json without applying restrictive OS-level file permissions (e.g., 0600 or owner-only), instead writing the file with world-readable or group-readable bits. This violates the principle of least privilege for sensitive configuration files. The CVSS 4.0 vector (AV:L/AT:P) reflects that exploitation is local and depends on a shared multi-user environment - consistent with shared hosting or multi-tenant server deployments. The affected product is identified via CPE as cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*, covering all OpenClaw versions prior to 2026.4.24.

RemediationAI

The primary fix is to upgrade to OpenClaw version 2026.4.24 or later, which resolves the insecure permission assignment in the config recovery path. The vendor security advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-rwp6-7w3q-75fq and the VulnCheck advisory at https://www.vulncheck.com/advisories/openclaw-insecure-file-permissions-in-config-recovery-via-openclaw-json should be consulted for patch details. If immediate upgrade is not possible, administrators on shared hosts should manually harden the permissions of OpenClaw.json after any recovery event using 'chmod 600 OpenClaw.json' and 'chown <openclaw-user>:<openclaw-user> OpenClaw.json' to restrict read access to the owning user only. Additionally, avoid running OpenClaw on shared multi-user hosts without file-system-level isolation (e.g., separate OS users, containers, or chroot environments) until the patch is applied, as these controls eliminate the shared-access condition that AT:P depends upon.