Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-56pc-6hvp-4gv4
No affected components available
Vulnerability
Path traversal in config $include resolution allowed arbitrary local file reads outside the config directory boundary (CWE-22).
Attack Vectors
- If an attacker can modify OpenClaw config, they can set
$includeto absolute paths (for example/etc/passwd) and read files accessible to the OpenClaw process. - If an attacker can modify OpenClaw config, they can use traversal paths (for example
../../...) to escape the config directory. - If an attacker can create symlinks inside the config directory, they can point includes to external files unless real-path checks are enforced.
- Impact scope is bounded by the file permissions of the OpenClaw runtime user; this is not an unauthenticated remote-only vector by itself.
Impact
A successful exploit can expose local secrets and credentials readable by the OpenClaw process user, including API keys and private config material.
Affected Packages / Versions
- Package:
openclaw(npm) - Vulnerable versions:
<=2026.2.15 - Patched versions:
>=2026.2.17
Fix Commit(s)
d1c00dbb7c64a39e205464dae7f2a068420e91c1
Release Process Note
Patched version is pre-set to 2026.2.17. Once npm release 2026.2.17 is available, this advisory is ready to publish.
OpenClaw thanks @aether-ai-agent for reporting.
The vulnerability requires local access to the device to be exploited. It is easy for an attacker to exploit this vulnerability. An attacker needs high-level or administrative privileges. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a high impact on the confidentiality of the information.
Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard