MEDIUM 6.5

CVE-2026-53825: OpenClaw Arbitrary File Read in Memory-Wiki Ingest (MEDIUM)

OpenClaw versions prior to 2026.4.7 contain a file-reading vulnerability in the memory-wiki ingest feature. Users with operator.write permissions can exploit this to read files from the local system that fall outside the intended ingest sources, potentially accessing sensitive configuration files, credentials, or other protected data. The vulnerability requires authenticated access and operator-level permissions, limiting its reach but increasing risk for multi-tenant or federated deployments where gateway operators may be less trusted.

Source data · NVD / CISA · public domain

CVSS
3.1 · 6.5 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Weaknesses (CWE)
CWE-22
Affected products
1 configuration(s)
Published / Modified
2026-06-12 / 2026-06-17

NVD description (verbatim)

OpenClaw before 2026.4.7 contains an arbitrary file read vulnerability in the memory-wiki ingest feature that allows authenticated Gateway operators with operator.write scope to read local files outside intended ingest sources. Attackers with operator.write access can specify arbitrary local file paths to import file content into wiki memory, bypassing access restrictions.

2 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-53825 is a path traversal vulnerability (CWE-22) in OpenClaw's memory-wiki ingest mechanism. The feature fails to properly validate or sanitize file path inputs when authenticated users with operator.write scope attempt to import wiki content. This allows an attacker to specify absolute or relative paths to arbitrary locations on the filesystem, bypassing directory-level access controls. The vulnerability is reachable over the network from any authenticated operator, with no user interaction required. The CVSS 3.1 score of 6.5 (Medium) reflects high confidentiality impact but no integrity or availability risk.

Business impact

Unauthorized access to sensitive local files poses a data breach risk, particularly in environments where OpenClaw stores configuration secrets, database credentials, API keys, or intellectual property within accessible directories. For organizations using OpenClaw as a central information platform, this could expose data across multiple connected systems. The impact is bounded by the filesystem permissions available to the OpenClaw process and the location of sensitive assets, but the ease of exploitation by any operator with write scope makes it a notable insider-risk vector.

Affected systems

OpenClaw versions before 2026.4.7 are affected. All deployments running older versions where authenticated users (gateway operators with operator.write permissions) are present face potential risk. The vulnerability does not affect unauthenticated users or operators without write scope.

Exploitability

Exploitation requires valid authentication and operator.write privilege—a relatively low bar in many deployments, especially where gateway operators are provisioned broadly. No user interaction is needed; the attacker can directly invoke the ingest feature with a crafted file path. Network accessibility is straightforward for any authenticated user. The lack of complexity in crafting exploitation payloads and the absence of code obfuscation make this practical to exploit once access is obtained.

Remediation

Update OpenClaw to version 2026.4.7 or later. This version implements proper input validation and path normalization in the memory-wiki ingest feature to prevent directory traversal. Organizations should verify patching against the official OpenClaw advisory. Until patched, restrict operator.write scope to users who genuinely require it, and monitor ingest activity logs for suspicious file path references.

Patch guidance

Apply the update to OpenClaw 2026.4.7 or later. Verify the patch against the official OpenClaw security advisory to confirm the exact affected version range and any conditional fixes. Test patching in a non-production environment first, particularly if custom ingest workflows depend on the gateway operator role. Consider using your package manager or automated update tooling to ensure consistent patching across all deployed instances.

Detection guidance

Monitor OpenClaw ingest logs and system-level file access patterns for the following indicators: (1) ingest requests specifying paths with ../ sequences or absolute paths outside expected ingest directories, (2) access to sensitive system paths such as /etc, /var, or configuration directories, (3) sudden spikes in file-read operations by gateway operators, (4) file access patterns that deviate from normal wiki ingest behavior. Correlate with authentication logs to identify which operators are executing unusual ingest operations.

Why prioritize this

This vulnerability merits prioritization because it affects authenticated users with moderately common permissions, enables disclosure of high-value secrets, and can be exploited remotely with no user interaction. While the CVSS score is Medium, the practical risk is elevated in environments where operators are less carefully scoped or where sensitive data is stored within OpenClaw's filesystem reach. Organizations with multiple gateway operators should patch quickly to reduce insider-risk surface area.

Risk score, explained

The CVSS 3.1 score of 6.5 reflects: (1) network-accessible attack vector (AV:N), (2) low attack complexity requiring no exploitation tricks (AC:L), (3) requirement for prior authenticated access and elevated permissions (PR:L), (4) no user interaction needed (UI:N), (5) no scope elevation outside the OpenClaw process (S:U), (6) high confidentiality impact from arbitrary file read (C:H), and (7) no integrity or availability impact (I:N, A:N). The score appropriately captures that this is a serious confidentiality leak for authenticated attackers but not an emergency—it does not enable lateral movement, denial of service, or system compromise without additional context.

Frequently asked questions

Who can exploit this vulnerability?

Any OpenClaw user with operator.write scope can exploit it, assuming they have valid authentication. This is typically gateway operators or users with explicit operator role assignments. Users without operator.write permissions are not affected.

Does this vulnerability allow remote code execution or system takeover?

No. This vulnerability is limited to reading arbitrary local files. It does not permit writing, deleting, executing code, or escalating privileges. The impact is disclosure only.

How can I check if we are affected?

Check your OpenClaw version using the admin console or package manager output. Versions before 2026.4.7 are affected. If you are running 2026.4.7 or later, you have the fix.

What should I do if I cannot patch immediately?

Restrict operator.write scope to only essential users, enable detailed audit logging of ingest operations, monitor for suspicious file path patterns, and consider network segmentation to limit authenticated access to the OpenClaw instance until you can apply the patch.

This analysis is provided for informational purposes and reflects the vulnerability description and CVSS assessment as of the publication and modification dates. Verify all version numbers, patch availability, and vendor guidance directly against the official OpenClaw security advisory before deploying patches. SEC.co does not provide legal advice; consult your legal and compliance teams regarding disclosure obligations or regulatory reporting. No exploit code or detailed attack methodology is provided herein. Source: NVD (public-domain), retrieved 2026-07-20. Analysis generated by SEC.co (claude-haiku-4-5).