What is CVE-2026-35662?

CVE-2026-35662 is a medium-severity missing authorization vulnerability in openclaw (npm), affecting versions < 2026.3.22. It is fixed in 2026.3.22. The application does not perform an authorization check before performing a sensitive operation.

How severe is CVE-2026-35662?

CVE-2026-35662 has a CVSS score of 4.3 (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.

Which versions of openclaw are affected by CVE-2026-35662?

openclaw (npm) versions < 2026.3.22 is affected.

Is there a fix for CVE-2026-35662?

Yes. CVE-2026-35662 is fixed in 2026.3.22. Upgrade to this version or later.

Is CVE-2026-35662 exploitable, and should I be worried?

Whether CVE-2026-35662 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.

What actually determines whether CVE-2026-35662 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.

CVE-2026-35662 in openclaw | Intelligent Application Security

Q: How severe is CVE-2026-35662?

CVE-2026-35662 has a CVSS score of 4.3 (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.

Q: Which versions of openclaw are affected by CVE-2026-35662?

openclaw (npm) versions < 2026.3.22 is affected.

Q: Is there a fix for CVE-2026-35662?

Yes. CVE-2026-35662 is fixed in 2026.3.22. Upgrade to this version or later.

Q: Is CVE-2026-35662 exploitable, and should I be worried?

Whether CVE-2026-35662 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.

Q: What actually determines whether CVE-2026-35662 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.

Q: How do I fix CVE-2026-35662?

Upgrade openclaw to 2026.3.22 or later.

Summary

Leaf subagents could still use the send action to message controlled child sessions even when their controlScope was narrower than children.

Affected Packages / Versions

Package: openclaw (npm)
Affected: < 2026.3.22
Fixed: >= 2026.3.22
Latest released tag checked: v2026.3.23-2 (630f1479c44f78484dfa21bb407cbe6f171dac87)
Latest published npm version checked: 2026.3.23-2

Fix Commit(s)

7679eb375294941b02214c234aff3948796969d0

Release Status

The fix shipped in v2026.3.22 and remains present in v2026.3.23 and v2026.3.23-2.

Code-Level Confirmation

src/auto-reply/reply/commands-subagents/action-send.ts now threads controller context through the send path.
src/agents/subagent-control.ts now blocks send attempts unless the requester owns the target and has controlScope="children".

OpenClaw thanks @space08 for reporting.

Impact

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

CVE-2026-35662 has a CVSS score of 4.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. 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.22); upgrading removes the vulnerable code path.

Affected versions

openclaw (< 2026.3.22)

Security releases

openclaw → 2026.3.22 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Upgrade openclaw to 2026.3.22 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-35662? CVE-2026-35662 is a medium-severity missing authorization vulnerability in openclaw (npm), affecting versions < 2026.3.22. It is fixed in 2026.3.22. The application does not perform an authorization check before performing a sensitive operation.
How severe is CVE-2026-35662? CVE-2026-35662 has a CVSS score of 4.3 (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.
Which versions of openclaw are affected by CVE-2026-35662? openclaw (npm) versions < 2026.3.22 is affected.
Is there a fix for CVE-2026-35662? Yes. CVE-2026-35662 is fixed in 2026.3.22. Upgrade to this version or later.
Is CVE-2026-35662 exploitable, and should I be worried? Whether CVE-2026-35662 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
What actually determines whether CVE-2026-35662 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.
How do I fix CVE-2026-35662? Upgrade openclaw to 2026.3.22 or later.

Other vulnerabilities in openclaw

CVE-2026-53811 CVE-2026-53816 CVE-2026-53806 CVE-2026-53818 CVE-2026-53809