GHSA-2ch6-x3g4-7759: Openclaw OpenClaw's Commands.allowFrom Sender Authorization Accepted Vulnerability
HIGHGHSA-2ch6-x3g4-7759 is a HIGH openclaw's commands.allowfrom sender authorization accepted vulnerability (CWE-639: Authorization Bypass Through User-Controlled Key) affecting Openclaw libraries in the npm ecosystem. The issue involves openclaw's commands.allowfrom sender authorization accepted conversation identifiers via ctx.from. Remediation is available by upgrading affected packages to version 2026.2.23.
GHSA-2ch6-x3g4-7759 at a Glance
How to Fix GHSA-2ch6-x3g4-7759
To remediate this vulnerability, upgrade all affected Openclaw dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install openclaw@2026.2.23Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls openclawHow to Check if You Are Affected
To determine whether your Node.js application is affected by GHSA-2ch6-x3g4-7759, inspect your project dependencies using npm:
npm ls openclawAnalyze the terminal output to locate any version of Openclaw in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2026.2.23), your application is affected.
Note: The npm ls openclaw command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-639: Authorization Bypass Through User-Controlled Key, where the system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. In Openclaw, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
GHSA-2ch6-x3g4-7759 Affected Openclaw Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
openclaw
|
npm |
< 2026.2.23
|
2026.2.23
|
References
Frequently Asked Questions
What is GHSA-2ch6-x3g4-7759?
Which Openclaw versions are affected?
What version fixes GHSA-2ch6-x3g4-7759?
Is openclaw affected?
What CWE is associated with GHSA-2ch6-x3g4-7759?
How can I check npm dependencies for GHSA-2ch6-x3g4-7759?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-2ch6-x3g4-7759",
"modified" : "2026-03-03T23:19:46Z",
"published" : "2026-03-03T23:19:46Z",
"aliases" : [ ],
"summary" : "OpenClaw's commands.allowFrom sender authorization accepted conversation identifiers via ctx.From",
"details" : "### Summary\n`commands.allowFrom` is documented as a sender authorization allowlist for commands/directives, but command authorization could include `ctx.From` (conversation identity) as a sender candidate.\n\nWhen `commands.allowFrom` contained conversation-like identifiers (for example Discord `channel:<id>` or WhatsApp group JIDs), command/directive authorization could be granted to participants in that conversation instead of only the intended sender identity.\n\n### Affected Packages / Versions\n- Package: `openclaw` (npm)\n- Affected versions: `<= 2026.2.22-2`\n- Patched version: `2026.2.23` (released)\n\n### Details\nRoot cause: `resolveSenderCandidates()` in `src/auto-reply/command-auth.ts` always included `ctx.From` in candidate evaluation used by `commands.allowFrom` authorization checks.\n\n`ctx.From` is sender-like in some direct-message contexts, but conversation-like in channel/group/thread contexts. This mixed principal handling allowed conversation identifiers to satisfy sender-only authorization.\n\n### Impact\nIn affected versions, command/directive authorization could become broader than intended when operators configured `commands.allowFrom` with conversation identifiers, allowing unintended users in that conversation to run command-only/directive-only flows.\n\n### Fix\nMain branch now treats `commands.allowFrom` as sender-only:\n- `ctx.From` is no longer included as a general sender candidate.\n- `ctx.From` is only used as fallback when sender fields are absent and the value is not conversation-shaped.\n- Regression tests were added for conversation-id denial and direct-message fallback preservation.\n\n### Fix Commit(s)\n- `08e2aa44e78a9c946d97bea62304e6f533b8fa8e`\n\n### Release Process Note\n`patched_versions` is pre-set to the released version (`2026.2.23`). This advisory now reflects released fix version `2026.2.23`.\n\nOpenClaw thanks @jiseoung for reporting.",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "openclaw"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "2026.2.23"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/openclaw/openclaw/security/advisories/GHSA-2ch6-x3g4-7759"
}, {
"type" : "WEB",
"url" : "https://github.com/openclaw/openclaw/commit/08e2aa44e78a9c946d97bea62304e6f533b8fa8e"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/openclaw/openclaw"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-639" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-03-03T23:19:46Z",
"nvd_published_at" : null
}
}