CVE-2026-41329: OpenClaw: Heartbeat context inheritance bypasses sandbox via senderIsOwner escalation
OpenClaw 2026.3.28 and earlier let a heartbeat run triggered by a command's completion inherit owner status from the session's delivery target. Output from node exec then reaches owner-only tools, which bypasses the sandbox boundary. The maintainers rate it critical. Upgrade to openclaw 2026.3.31.
Published Apr 2, 2026 · Updated Apr 21, 2026 · Analysis Oct 30, 2026
What an attacker can do
After an exec command finishes, OpenClaw can start a heartbeat run so the agent reacts to the result. In runHeartbeatOnce (src/infra/heartbeat-runner.ts) that run took its context from the session. resolveCommandAuthorization in src/auto-reply/command-auth.ts then computed senderIsOwner from the identity, scope or owner-allow-all settings, and the exec-event run could end up counted as the owner, though the text it carried was command output and not an owner message.
Output of a command can contain attacker-controlled text: a fetched web page, a file from a cloned repository, a message from a remote node. If that text ends up as input to an owner-privileged turn, it can steer the agent to call owner-only tools that the sandbox would otherwise withhold. That is a privilege escalation across the sandbox boundary. The CVSS 4.0 vector shows network reach, low privileges and high impact on confidentiality, integrity and availability, including subsequent systems. The attack needs a precondition, such as getting your agent to run a command whose output the attacker influences. The advisory text does not give a worked exploit.
Who is affected
The npm package openclaw at 2026.3.28 and earlier, where agents run exec commands and heartbeat runs follow their completion. Version 2026.3.31 is the first stable release with the fix.
Check your install:
npm ls -g openclaw
openclaw --versionThe higher the privilege of the owner tool surface in your deployment, the larger the exposure.
openclaw
- Ecosystem
- npm
- Affected
- <= 2026.3.28
- Fixed in
- 2026.3.31
- Check
npm ls openclaw
How to fix it
Upgrade to openclaw 2026.3.31 or later.
npm install -g [email protected]Commit a30214a6 adds a ForceSenderIsOwnerFalse flag to MsgContext, a trusted system override. runHeartbeatOnce sets it to true for exec-completion runs, and resolveCommandAuthorization then returns senderIsOwner false whatever the identity or scope says. Exec output stays on the non-owner tool surface. Other contexts are unchanged. The advisory names no workaround.
How to tell if you were hit
Review agent session logs for owner-only tool calls that happened in a turn started by an exec-event heartbeat, rather than by a message from the owner. Look at what the preceding command output contained, such as injected instructions in fetched content. Check for unexpected changes to config, outbound messages or file writes made around those turns. Beam, if you run it next to the agent, records agent shell commands and tool calls, which helps reconstruct what ran after a command finished.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
Summary
Heartbeat context inheritance bypasses sandbox via senderIsOwner escalation
Current Maintainer Triage
- Status: open
- Normalized severity: Critical
Affected Packages / Versions
- Package:
openclaw(npm) - Latest published npm version:
2026.3.31 - Vulnerable version range:
<=2026.3.28 - Patched versions:
>= 2026.3.31 - First stable tag containing the fix:
v2026.3.31
Fix Commit(s)
a30214a624946fc5c85c9558a27c1580172374fd— 2026-03-31T09:06:51+09:00
OpenClaw thanks @AntAISecurityLab for reporting.
Credited to AntAISecurityLab.
Questions
- Is OpenClaw 2026.3.28 affected by CVE-2026-41329?
Yes. Versions up to and including 2026.3.28 are vulnerable. The patched version is 2026.3.31.
- Why is it rated critical?
The maintainers rate it critical and the CVSS 4.0 score is 9.0, with high impact on confidentiality, integrity and availability. An exec output turn gained owner rights, so it could reach tools that should be limited to the owner.
- Is it exploited in the wild?
No source I read says so, and the entry has no CISA KEV flag. The EPSS score is about 0.3%.
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
