Summary
What this means (plain language)
If you give a client “chat/write” access to the gateway (operator.write) but you do not intend to let that client approve exec requests (operator.approvals), affected versions could still let that client approve/deny a pending exec approval by sending the /approve chat command.
This is mainly relevant for shared or multi-client setups where different tokens are intentionally scoped differently. Single-operator installs are typically less impacted.
Technical summary
A gateway client authenticated with a device token scoped only to operator.write (without operator.approvals) could approve/deny pending exec approval requests by sending a chat message containing the built-in /approve command.
exec.approval.resolve is correctly scoped to operator.approvals for direct RPC calls, but the /approve command path invoked it via an internal privileged gateway client.
Affected Packages / Versions
openclaw(npm):< 2026.2.2
Workarounds
- Upgrade to
openclaw >= 2026.2.2. - If you cannot upgrade: avoid issuing write-only device tokens to untrusted clients; disable text commands (
commands.text=false) or restrict access to the webchat/control UI.
References
- Fix:
src/auto-reply/reply/commands-approve.ts - Coverage:
src/auto-reply/reply/commands-approve.test.ts
Release Process Note
This advisory is kept in draft; once the fixed npm versions are available, it can be published without further edits.
Thanks @yueyueL for reporting.
Impact
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-28473 has a CVSS score of 7.2 (High). The vector is network-reachable, high 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.2); upgrading removes the vulnerable code path.
Affected versions
Security releases
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.
Remediation advice
- Fixed in
openclaw2026.2.2. - Fix commit(s):
efe2a464afcff55bb5a95b959e6bd9ec0fef086e. - Change: when
/approveis invoked from gateway clients (webchat/internal channel), it now requires the requesting client to haveoperator.approvals(oroperator.admin).
Frequently Asked Questions
- What is CVE-2026-28473? CVE-2026-28473 is a high-severity improper privilege management vulnerability in openclaw (npm), affecting versions < 2026.2.2. It is fixed in 2026.2.2. The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access.
- How severe is CVE-2026-28473? CVE-2026-28473 has a CVSS score of 7.2 (High). 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-28473? openclaw (npm) versions < 2026.2.2 is affected.
- Is there a fix for CVE-2026-28473? Yes. CVE-2026-28473 is fixed in 2026.2.2. Upgrade to this version or later.
- Is CVE-2026-28473 exploitable, and should I be worried? Whether CVE-2026-28473 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-28473 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-28473? Upgrade
openclawto 2026.2.2 or later.