CVE-2026-32035

In [email protected], the Discord voice transcript path called agentCommand(...) without senderIsOwner, and agentCommand defaults missing senderIsOwner to true.

This could allow a non-owner voice participant in the same channel to reach owner-only tool surfaces (gateway, cron) during voice transcript turns.

Security model note

OpenClaw’s documented trust model is a personal assistant model (one trusted operator), not an adversarial multi-user boundary.

• OpenClaw does not treat one shared gateway/chat surface as a hardened per-user auth boundary.
• Mixed-trust deployments (mutually untrusted users sharing one gateway/channel) are outside recommended deployment boundaries.

This report is treated as a valid hardening/authorization bug because owner-only tool policy should still be applied consistently across chat-driven turns, including Discord voice transcript ingress.

Details

Relevant path:

1. Voice transcript run omitted senderIsOwner in Discord voice manager.
2. Missing senderIsOwner defaulted to true in agentCommand.
3. Owner-only tool policy is keyed on senderIsOwner.
4. gateway and cron are owner-only tools.

Severity rationale

Downgraded from high to medium to align with OpenClaw’s trust model and deployment assumptions:

• Requires participation in the same voice environment as the trusted operator workflow.
• Requires Discord voice path conditions (joined voice channel + transcript flow).
• Does not introduce a new cross-gateway or unauthenticated boundary bypass.

Affected Packages / Versions

• Package: openclaw (npm)
• Affected versions: <= 2026.3.1
• Patched versions: >= 2026.3.2 (released)

• Affects deployments where Discord voice is enabled and the bot is present in channels with non-owner participants.
• No gateway-auth boundary bypass was required.
• Practical risk depends strongly on whether the deployment is single-trust (recommended) or mixed-trust (not recommended).

The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access. Typical impact: privilege escalation beyond the intended level.

CVE-2026-32035 has a CVSS score of 5.9 (Medium). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.3.2); upgrading removes the vulnerable code path.

Kodem intelligence

• Always pass explicit senderIsOwner from Discord voice transcript ingress.
• Fail closed (false) when owner status is unknown for non-local/chat ingress paths.
• Keep regression tests that verify owner/non-owner voice speaker handling.

1. What is CVE-2026-32035? CVE-2026-32035 is a medium-severity improper privilege management vulnerability in openclaw (npm), affecting versions <= 2026.3.1. It is fixed in 2026.3.2. The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access.
2. How severe is CVE-2026-32035? CVE-2026-32035 has a CVSS score of 5.9 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of openclaw are affected by CVE-2026-32035? openclaw (npm) versions <= 2026.3.1 is affected.
4. Is there a fix for CVE-2026-32035? Yes. CVE-2026-32035 is fixed in 2026.3.2. Upgrade to this version or later.
5. Is CVE-2026-32035 exploitable, and should I be worried? Whether CVE-2026-32035 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-32035 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-32035? Upgrade openclaw to 2026.3.2 or later.