openclaw
Affected
- introduced
0, fixed2026.2.22(semver)
Fixed versions
2026.2.22
Fix
- Fixed version
2026.2.22npm install [email protected]
Advisory
Also known as: None
OpenClaw's elevated allowFrom accepted broader identity signals than specified within sender-scoped authorization
Summary
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
openclaw (npm)2026.2.21-2<= 2026.2.21-22026.2.22Details
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)
6817c0ec7b4fa830123d4f5c340f075a4bd04ee2Release 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.
Medium Basis: The source's own band: MODERATE
0, fixed 2026.2.22 (semver)2026.2.22
2026.2.22npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0