CVE-2026-32898

Vulnerability Summary

The OpenClaw ACP client could auto-approve tool calls based on untrusted metadata and permissive name heuristics. A malicious or compromised ACP tool invocation could bypass expected interactive approval prompts for read-class operations.

Affected Packages / Versions

• Package: npm openclaw
• Affected published versions: <= 2026.2.22-2 (latest published as of February 24, 2026 is 2026.2.22-2)
• Patched in code on main: 2026.2.23 (released)

Technical Details

• Permission classification trusted incoming toolCall.kind and heuristic name matching.
• Non-core read-like names and spoofed kind metadata could reach auto-approve paths.
• read operations were not scoped strongly enough to cwd in all metadata/title forms.

Affected Functions

• resolvePermissionRequest
• resolveToolNameForPermission
• shouldAutoApproveToolCall

Fix Commit(s)

• 12cc754332f9a7c92e158ce7644aa22df79c0904
• 63dcd28ae0be2de1c75af09cc81841cebeec068f

Found using MCPwner

Thanks @nedlir 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-32898 has a CVSS score of 5.4 (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.2.23); upgrading removes the vulnerable code path.

Kodem intelligence

• Require trusted core tool IDs for auto-approval and ignore untrusted toolCall.kind as an authorization source.
• Scope read auto-approval to cwd-resolved paths.
• Add stricter tool-name validation and regression coverage for spoofed kind and non-core read-like names.

1. What is CVE-2026-32898? CVE-2026-32898 is a medium-severity incorrect authorization vulnerability in openclaw (npm), affecting versions <= 2026.2.22-2. It is fixed in 2026.2.23. 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-32898? CVE-2026-32898 has a CVSS score of 5.4 (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-32898? openclaw (npm) versions <= 2026.2.22-2 is affected.
4. Is there a fix for CVE-2026-32898? Yes. CVE-2026-32898 is fixed in 2026.2.23. Upgrade to this version or later.
5. Is CVE-2026-32898 exploitable, and should I be worried? Whether CVE-2026-32898 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-32898 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-32898? Upgrade openclaw to 2026.2.23 or later.