NewApp Monitoring is liveSign up free
AgentbeamBeta
AI agent vulnerability · OpenClaw

GHSA-p2fh-f5fc-44hr: OpenClaw: memory-wiki ingest could read local files with operator.write scope

mediumCVSS 3.1 6.5

OpenClaw's memory-wiki ingest tool let a Gateway caller with `operator.write` scope read arbitrary local file paths, not only the intended ingest sources, and import the content into wiki memory. Versions before 2026.5.12 are affected. Update the openclaw package to 2026.5.12 or later.

Published Jul 2, 2026 · Analysis Oct 25, 2026

What an attacker can do

The memory-wiki plugin ingests sources into the agent's wiki memory. It should read only from approved ingest sources. In affected versions, a caller with operator.write access to the plugin tool could point ingest at any local file path the Gateway process can read (CWE-732). The advisory names no parameter or function.

The attacker needs an authenticated Gateway connection with operator.write scope. The CVSS 3.1 vector is network, low complexity, low privileges, no user interaction, and high confidentiality impact only. Files such as SSH keys, environment files or config with tokens can be pulled into wiki memory. From there the agent or a later reader may read them back. A prompt-injected agent that holds the tool can do the same.

The advisory leaves OpenClaw's trusted-operator model unchanged. The risk is in setups where write scope is given to lower-trust users or agents.

Who is affected

Affected: npm openclaw before 2026.5.12, with the memory-wiki plugin enabled and reachable by a caller with operator.write.

npm ls -g openclaw

Drop -g for a project install. The advisory page also shows a different affected range (up to 2026.5.6) than the package data used here, so use the package data and upgrade to 2026.5.12 or later.

openclaw

Ecosystem
npm
Affected
< 2026.5.12
Fixed in
2026.5.12
Check
npm ls openclaw

How to fix it

Update to openclaw 2026.5.12.

npm install -g [email protected]

Until you can update, limit memory-wiki write access to trusted operators. The advisory also suggests narrow channel and tool allowlists, not sharing one Gateway between mutually untrusted users, and disabling the feature if you do not need it.

How to tell if you were hit

The advisory gives no log line. Search the wiki memory for content that looks like system files, key material or config, such as private key headers or environment variable dumps. Review memory-wiki ingest calls and the paths they named. List which operators and agents hold operator.write. Beam records agent file access and MCP tool calls, which can show an agent driving an ingest of sensitive files.

Original advisory

From the GitHub Advisory Database (CC BY 4.0).

Summary

memory-wiki ingest could read local files with operator.write scope. In affected versions, a Gateway caller with operator.write access to the plugin tool could read arbitrary local file paths instead of staying within the intended ingest sources.

This advisory is scoped to the named feature and configuration. It does not change OpenClaw's trusted-operator model: authenticated Gateway operators, installed plugins, and intentional local execution surfaces remain trusted unless a separate policy, approval, allowlist, sandbox, or auth boundary is crossed.

Impact

When the affected feature is enabled and reachable, this could import local file content into wiki memory. Practical impact depends on the operator's configuration and whether lower-trust input can reach that path.

Resolution

Update to a patched OpenClaw release when one is listed for this advisory. If the Patched versions field is populated, use that version or later.

Mitigations

limit memory-wiki write access to trusted operators until patched. As general hardening, keep channel and tool allowlists narrow, avoid sharing one Gateway between mutually untrusted users, and disable the affected feature when it is not needed.

Credited to Blee72.

Questions

What scope does an attacker need for the memory-wiki flaw?

A Gateway connection with operator.write access to the plugin tool. The CVSS vector lists low privileges and no user interaction.

Which OpenClaw version fixes it?

The package data lists 2026.5.12 as the patched version, with versions before it affected. The advisory page shows a different range, so check the release notes if you run a version close to that boundary.

What can be read?

Arbitrary local file paths that the Gateway process can read. The content is imported into wiki memory.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology

More OpenClaw vulnerabilities

All OpenClaw entries