GHSA-P2FH-F5FC-44HR

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.

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.

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.

A file, directory, or other resource is assigned permissions that allow broader access than intended. Typical impact: unauthorized read, modification, or execution of the resource.

GHSA-P2FH-F5FC-44HR has a CVSS score of 6.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.5.12); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is GHSA-P2FH-F5FC-44HR? GHSA-P2FH-F5FC-44HR is a medium-severity incorrect permission assignment for critical resource vulnerability in openclaw (npm), affecting versions < 2026.5.12. It is fixed in 2026.5.12. A file, directory, or other resource is assigned permissions that allow broader access than intended.
2. How severe is GHSA-P2FH-F5FC-44HR? GHSA-P2FH-F5FC-44HR has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of openclaw are affected by GHSA-P2FH-F5FC-44HR? openclaw (npm) versions < 2026.5.12 is affected.
4. Is there a fix for GHSA-P2FH-F5FC-44HR? Yes. GHSA-P2FH-F5FC-44HR is fixed in 2026.5.12. Upgrade to this version or later.
5. Is GHSA-P2FH-F5FC-44HR exploitable, and should I be worried? Whether GHSA-P2FH-F5FC-44HR is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-P2FH-F5FC-44HR is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-P2FH-F5FC-44HR? Upgrade openclaw to 2026.5.12 or later.