GHSA-f6h3-846h-2r8w: Openclaw OpenClaw's Elevated AllowFrom Accepted Broader Vulnerability

MODERATE
CWE-639
Published
Advisory Summary

GHSA-f6h3-846h-2r8w is a MODERATE openclaw's elevated allowfrom accepted broader vulnerability (CWE-639: Authorization Bypass Through User-Controlled Key) affecting Openclaw libraries in the npm ecosystem. The issue involves openclaw's elevated allowfrom accepted broader identity signals than specified within sender-scoped authorization. Remediation is available by upgrading affected packages to version 2026.2.22.

GHSA-f6h3-846h-2r8w at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-f6h3-846h-2r8w
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-639: Authorization Bypass Through User-Controlled Key
Affected Product Openclaw
Package Ecosystem npm
Published Date
Last Updated

How to Fix GHSA-f6h3-846h-2r8w

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.

openclaw fixed: 2026.2.22
npm install openclaw@2026.2.22
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls openclaw

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-f6h3-846h-2r8w, inspect your project dependencies using npm:

npm ls openclaw

Analyze 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.22), 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

### 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.

GHSA-f6h3-846h-2r8w Affected Openclaw Versions

1 component(s)
Fixed Versions:
2026.2.22
Product / Package Ecosystem Affected Versions Fixed Version
openclaw
npm
< 2026.2.22
2026.2.22

References

Frequently Asked Questions

What is GHSA-f6h3-846h-2r8w?
GHSA-f6h3-846h-2r8w is a security vulnerability in Openclaw involving OpenClaw's elevated allowFrom accepted broader identity signals than specified within sender-scoped authorization under CWE-639: Authorization Bypass Through User-Controlled Key.
Which Openclaw versions are affected?
Affected versions include releases prior to 2026.2.22 across affected packages: openclaw.
What version fixes GHSA-f6h3-846h-2r8w?
Upgrading to 2026.2.22 (or the latest patched release for your respective branch) resolves the vulnerability.
Is openclaw affected?
Yes, openclaw is affected in releases prior to 2026.2.22. Upgrade your dependency to 2026.2.22 or later.
What CWE is associated with GHSA-f6h3-846h-2r8w?
GHSA-f6h3-846h-2r8w is classified under CWE-639: Authorization Bypass Through User-Controlled Key (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.).
How can I check npm dependencies for GHSA-f6h3-846h-2r8w?
Run the dependency tree command: 'npm ls openclaw'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-f6h3-846h-2r8w",
  "modified" : "2026-03-04T18:58:07Z",
  "published" : "2026-03-04T18:58:07Z",
  "aliases" : [ ],
  "summary" : "OpenClaw's elevated allowFrom accepted broader identity signals than specified within sender-scoped authorization",
  "details" : "### Summary\nIn 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.\n\n### Context\nOpenClaw 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.\n\n### Affected Packages / Versions\n- Package: `openclaw` (npm)\n- Latest published npm version at triage: `2026.2.21-2`\n- Affected versions: `<= 2026.2.21-2`\n- Planned patched version (pre-set for publish-ready advisory): `2026.2.22`\n\n### Details\nElevated 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`.\n\nMutable sender metadata (`SenderName`, `SenderUsername`, `SenderTag`) now requires explicit allowlist prefixes (`name:`, `username:`, `tag:`). Explicit identity prefixes are also supported (`id:`, `from:`, `e164:`).\n\n### Fix Commit(s)\n- `6817c0ec7b4fa830123d4f5c340f075a4bd04ee2`\n\n### Release Process Note\nThe 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.\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:L/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "openclaw"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2026.2.22"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/openclaw/openclaw/security/advisories/GHSA-f6h3-846h-2r8w"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openclaw/openclaw/commit/6817c0ec7b4fa830123d4f5c340f075a4bd04ee2"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/openclaw/openclaw"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-639" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-04T18:58:07Z",
    "nvd_published_at" : null
  }
}