GHSA-f6h3-846h-2r8w
OpenClaw's elevated allowFrom accepted broader identity signals than specified within sender-scoped authorization
GHSA-f6h3-846h-2r8w is a medium vulnerability (CVSS 5.3) in openclaw, published March 4, 2026. No source lists public exploit code. Fixed in openclaw 2026.2.22.
- Severity
- 5.3 MediumCVSS 4.0, GitHub Advisories
- Exploit chance
- UnscoredNo EPSS score yet
- Exploitation
- None knownNot on CISA’s or ENISA’s lists
- Fixed in
2026.2.22openclaw
Description
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
- 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 openclaw@2026.2.22 is published, this advisory can be published without additional content edits.
OpenClaw thanks @jiseoung for reporting.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
Affected packages
| Package | Affected | Fixed |
|---|---|---|
openclawnpm | before 2026.2.22 | 2026.2.22 |
What each source reports
GitHub Advisories Score used
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
- 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 openclaw@2026.2.22 is published, this advisory can be published without additional content edits.
OpenClaw thanks @jiseoung for reporting.
- Record
GHSA-f6h3-846h-2r8w- CVSS 4.0
- 5.3 Medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N - Weakness
- CWE-639
- Updated
- 2026-11-02
OSV
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
- 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 openclaw@2026.2.22 is published, this advisory can be published without additional content edits.
OpenClaw thanks @jiseoung for reporting.
- Record
GHSA-f6h3-846h-2r8w- CVSS 4.0
- 5.3 Medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N - Weakness
- CWE-639
- Updated
- 2026-11-02
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.