Summary
OpenClaw's elevated allowFrom accepted broader identity signals than specified within sender-scoped authorization
In certain elevated-mode configurations, tools.elevated.allowFrom accepted broader identity signals than intended. The fix tightens matching to sender-scoped identity by default and makes mutable metadata matching explicit.
Context
OpenClaw is commonly used in 1:1 chats or trusted group chats. In that intended model, this issue is best treated as authorization hardening / defense-in-depth for elevated sender approval.
Affected Packages / Versions
- Package:
openclaw(npm) - Latest published npm version at triage:
2026.2.21-2 - Affected versions:
<= 2026.2.21-2 - Planned patched version (pre-set for publish-ready advisory):
2026.2.22
Details
Elevated sender authorization now matches sender-scoped identity values only by default (SenderId, From, SenderE164) and no longer considers recipient routing fields such as ctx.To.
Mutable sender metadata (SenderName, SenderUsername, SenderTag) now requires explicit allowlist prefixes (name:, username:, tag:). Explicit identity prefixes are also supported (id:, from:, e164:).
Fix Commit(s)
6817c0ec7b4fa830123d4f5c340f075a4bd04ee2
Release Process Note
The advisory patched_versions is pre-set to the planned next release (2026.2.22). Once npm [email protected] is published, this advisory can be published without additional content edits.
OpenClaw thanks @jiseoung for reporting.
Impact
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.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-F6H3-846H-2R8W? GHSA-F6H3-846H-2R8W is a medium-severity security vulnerability in openclaw (npm), affecting versions < 2026.2.22. It is fixed in 2026.2.22.
- Which versions of openclaw are affected by GHSA-F6H3-846H-2R8W? openclaw (npm) versions < 2026.2.22 is affected.
- Is there a fix for GHSA-F6H3-846H-2R8W? Yes. GHSA-F6H3-846H-2R8W is fixed in 2026.2.22. Upgrade to this version or later.
- Is GHSA-F6H3-846H-2R8W exploitable, and should I be worried? Whether GHSA-F6H3-846H-2R8W 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 GHSA-F6H3-846H-2R8W 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 GHSA-F6H3-846H-2R8W? Upgrade
openclawto 2026.2.22 or later.