GHSA-5h2c-8v84-qpvr: OpenClaw shell-env fallback trusted startup env and could execute attacker-influenced login-shell paths
Summary OpenClaw shell-env fallback trusted startup environment values and could execute attacker-influenced login-shell startup paths before loading env keys. Affected Packages / Versions - Package: openclaw (npm) - Affected versions: = 2026.1.5 and <= 2026.2.21-2 - Fixed on main: 9363c320d8ffe29290906752fab92621da02c3f7 - Planned patched release version (pre-set): 2026.2.22 Details The vulnerable chain was in the…
Published Mar 3, 2026
Affected packages
openclaw
- Ecosystem
- npm
- Affected
- < 2026.2.22
- Fixed in
- 2026.2.22
- Check
npm ls openclaw
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
OpenClaw shell-env fallback trusted startup environment values and could execute attacker-influenced login-shell startup paths before loading env keys.
Affected Packages / Versions
- Package:
openclaw(npm) - Affected versions:
>= 2026.1.5and<= 2026.2.21-2 - Fixed on
main:9363c320d8ffe29290906752fab92621da02c3f7 - Planned patched release version (pre-set):
2026.2.22
Details
The vulnerable chain was in the shell-env fallback path:
src/infra/shell-env.tsresolveShell(env)trustedenv.SHELLwhen set.execLoginShellEnvZero(...)executed${SHELL} -l -c "env -0"with inherited runtime env.
src/config/io.ts- Config env values were applied before shell fallback execution.
src/config/env-vars.ts/ env policy coverageSHELLhandling was hardened, but startup-path selectors (HOME,ZDOTDIR) still needed explicit blocking in config env ingestion and sanitization for shell fallback execution.
With env/config influence, this could trigger unintended command execution in shell startup processing on the OpenClaw host process context.
Fix
Mainline hardening now:
- blocks
SHELL,HOME, andZDOTDIRduring config env ingestion used by runtime fallback, - sanitizes shell fallback execution env, pinning
HOMEto the real user home and droppingZDOTDIR+ dangerous startup vars, - adds regression tests for config env ingestion and shell fallback/path-probe sanitization.
Fix Commit(s)
9363c320d8ffe29290906752fab92621da02c3f7
Impact
- Local code-execution risk in environments where attacker-controlled env/config input can reach shell-env fallback.
- Under OpenClaw trust assumptions (
SECURITY.md), this is not a public-remote issue and depends on crossing local trusted-operator boundaries.
Release Process Note
patched_versions is intentionally pre-set to the planned next release (2026.2.22) so once npm release is out, maintainers can publish advisory immediately.
OpenClaw thanks @tdjackey for reporting.
Credited to tdjackey.
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. No analysis has been written for this entry yet. Methodology
More OpenClaw vulnerabilities
All OpenClaw entriesCVE-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, 2026CVE-2026-53812
OpenClaw's browser act interactions could bypass private-network navigation checks
medium7.7Jul 2, 2026
