Quick answers
- Is CVE-2026-41329 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-41329 being exploited in the wild.
- How severe is CVE-2026-41329?
- Critical severity, with a CVSS score of 9.9, published 21 April 2026.
- Which products and versions are affected?
- Openclaw <=2026.3.28.
- Is there a fix for CVE-2026-41329?
- A patch was published on 2026-03-31: Version 2026.3.31 contains the fix Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-41329 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-41329?
- Check whether you run Openclaw at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an authorization bypass (CWE-863) in OpenClaw's heartbeat context handling logic. The senderIsOwner privilege check is incorrectly inherited across heartbeat event contexts, allowing non-owner users to execute operations with owner-level permissions when they craft malicious heartbeat messages. The flaw requires authenticated network access but has no additional prerequisites. An attacker can read, modify, or delete arbitrary data and execute commands with elevated privileges. The issue is patched in version 2026.3.31 and later.
Affected products
- OpenClaw openclaw <=2026.3.28
Identifiers
- CVE-2026-41329
- GHSA-g5cg-8x5w-7jpm
Timeline
- 2026-04-02: disclosed
- 2026-03-31: patched: Version 2026.3.31 contains the fix