CVE-2026-53819: OpenClaw: Workspace .env could override Homebrew executable selection for skill install flows
In OpenClaw before 2026.5.27, a `.env` file in a workspace could override which Homebrew executable the skill install helper runs. A repository opened by a trusted operator could make skill setup launch an unintended Homebrew-compatible program. Upgrade to openclaw 2026.5.27.
Published Jul 2, 2026 · Analysis Oct 25, 2026
What an attacker can do
OpenClaw's skill install flows call a Homebrew executable. Before the fix, the workspace .env was allowed to influence which executable was chosen. That is an untrusted search path problem (CWE-426): the choice of program to run came from a file inside a repository the operator merely opened.
The attack therefore needs a malicious or tampered repository plus an operator who opens it and runs a skill install from that workspace. The CVSS vector marks user interaction as required. The result is the execution of an attacker-chosen program with the operator's privileges, so a cloned repository can become code execution on the machine running OpenClaw.
The advisory limits its scope. It does not change OpenClaw's trusted-operator model, and it says practical impact depends on the configuration and on whether lower-trust input can reach that path. The sources do not name the exact .env variable or the function involved.
Who is affected
The npm package openclaw in all versions before 2026.5.27, when the skill install feature is enabled and reachable and the operator works in a workspace holding an untrusted .env.
npm ls openclawUse npm ls -g openclaw for a global install. A version below 2026.5.27 is affected.
openclaw
- Ecosystem
- npm
- Affected
- < 2026.5.27
- Fixed in
- 2026.5.27
- Check
npm ls openclaw
How to fix it
Upgrade to [email protected], the first stable patched version:
npm install [email protected]Until then, the advisory says to avoid running skill install flows from untrusted workspaces. As general hardening it advises narrow channel and tool allowlists, not sharing one Gateway between mutually untrusted users, and disabling the affected feature when you do not need it.
How to tell if you were hit
Inspect .env files in workspaces where you ran skill installs, and look for entries that point to a Homebrew path or binary outside your normal Homebrew prefix. Check process history around skill setup for unexpected executables started by OpenClaw. The sources give no log line for this flaw. A cloned repository that ships a .env you did not write is the first thing to review.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
Summary
Workspace .env could override Homebrew executable selection for skill install flows. In affected versions, a workspace .env in a repository opened by a trusted operator could override the Homebrew executable used by the install helper.
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 run an unintended Homebrew-compatible executable during skill setup. Practical impact depends on the operator's configuration and whether lower-trust input can reach that path.
Patched Versions
The first stable patched version is 2026.5.27.
Mitigations
avoid running skill install flows from untrusted workspaces 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 feynman-hou.
Questions
- Does this need user interaction?
Yes. The CVSS vectors mark user interaction as required. An operator has to open the repository and run a skill install flow from that workspace.
- Which OpenClaw version fixes CVE-2026-53819?
2026.5.27 is the first stable patched version. Earlier versions are affected.
- Is a workaround available?
Yes. Avoid running skill install flows from untrusted workspaces and disable the affected feature if you do not need it. Upgrading is the real fix.
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 entriesCVE-2026-62197
OpenClaw: Browser CDP discovery could accept blocked WebSocket URLs
medium8.5Oct 21, 2026CVE-2026-35630
OpenClaw: QQBot native approval buttons did not enforce configured approver identity
high8.0Jul 2, 2026CVE-2026-53806
OpenClaw: Combined POSIX shell options could confuse exec revalidation
high8.8Jul 2, 2026CVE-2026-53809
OpenClaw: Embedded runner policy could be confused by provider aliases
medium3.8Jul 2, 2026CVE-2026-53810
OpenClaw's marketplace runtime extension metadata could point at unscanned payloads
high8.8Jul 2, 2026CVE-2026-53811
OpenClaw: Matrix allowFrom could bind to mutable display names
high8.8Jul 2, 2026
