CVE-2026-44118 Owner Impersonation via senderIsOwner
Older versions of OpenClaw (before 2026.4.22) trust a simple flag called senderIsOwner=true without checking who actually sent it, as long as the connection comes from the same machine (loopback). Any process running locally can set this flag and be treated as the gateway owner, gaining elevated privileges it shouldn't have.
How the attack works
An attacker who can run any process on the same host as OpenClaw — even a low-privilege one — connects to it over loopback (localhost). That process sends a message containing senderIsOwner=true. OpenClaw accepts this claim without verifying identity, and grants the sender owner-level privileges on the gateway. From there the attacker can use those privileges to control or manipulate the gateway as if they were its legitimate owner.
Netzilo detection
Netzilo reports this behaviour when it is observed.
- Signature ID
- netzilo-cve-2026-44118-001
- Severity
- Critical
- CVEs
- CVE-2026-44118
Why it matters
An organization loses control over which processes can act as the trusted gateway owner. This is a straightforward local privilege escalation: any code able to reach the loopback interface can impersonate the owner and bypass authorization checks, with no legitimate use case for that flag existing in normal traffic.
What you can do
- →Upgrade OpenClaw to version 2026.4.22 or later, which fixes this trust flaw.
- →Until patched, restrict which local processes and users can reach the OpenClaw loopback port.
- →Monitor for senderIsOwner=true appearing in payload content, since the rule notes it has no legitimate use.
- →Review what runs on hosts alongside OpenClaw and reduce the number of untrusted or unnecessary local processes.
Known benign look-alikes
- None expected — senderIsOwner=true has no legitimate use in external content