CVE-2026-32016

On macOS node-host, optional exec-approval allowlist mode previously treated basename-only entries (for example echo) as trusted command matches.
This could allow a same-name local binary (for example ./echo) to run without approval under security=allowlist + ask=on-miss.

Scope / Preconditions

• macOS node-host path.
• Optional exec approvals feature enabled with security=allowlist.
• Basename-only allowlist entries configured.

Default install posture is not impacted: security=deny by default.

Affected Packages / Versions

• Package: openclaw (npm)
• Latest published npm version at triage time: 2026.2.21-2
• Vulnerable range: <=2026.2.21-2
• Planned patched version (next release): >= 2026.2.22

Fix Commit(s)

• dd41fadcaf58fd9deb963d6e163c56161e7b35dd

Release Process Note

Patched version is pre-set for the planned next release (2026.2.22). Once that npm release is out, advisory can be published without further field edits.

OpenClaw thanks @tdjackey for reporting.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

CVE-2026-32016 has a CVSS score of 7.8 (Medium). The vector is requires local access, 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.2.22); upgrading removes the vulnerable code path.

Kodem intelligence

• Enforced path-only allowlist matching on macOS node-host (basename fallback removed).
• Added migration for legacy basename allowlist entries to last-resolved paths when available.
• UI/store validation now rejects non-path allowlist patterns.

1. What is CVE-2026-32016? CVE-2026-32016 is a medium-severity incorrect authorization vulnerability in openclaw (npm), affecting versions < 2026.2.22. It is fixed in 2026.2.22. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. How severe is CVE-2026-32016? CVE-2026-32016 has a CVSS score of 7.8 (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-32016? openclaw (npm) versions < 2026.2.22 is affected.
4. Is there a fix for CVE-2026-32016? Yes. CVE-2026-32016 is fixed in 2026.2.22. Upgrade to this version or later.
5. Is CVE-2026-32016 exploitable, and should I be worried? Whether CVE-2026-32016 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-32016 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-32016? Upgrade openclaw to 2026.2.22 or later.