GHSA-8JHH-JCQG-MJ5P

In affected versions of openclaw, channel-initiated config mutations were authorized against the originating account's configWrites policy but did not consistently re-check the targeted account scope. An authorized sender on one account could mutate protected sibling-account configuration when the target account had configWrites: false.

Affected Packages and Versions

• Package: openclaw (npm)
• Affected versions: <= 2026.3.8
• Fixed in: 2026.3.11

Technical Details

The mutation path validated the origin account scope but did not consistently authorize every resolved target scope. Ambiguous collection and root writes under channels and channels.<provider>.accounts could therefore reach protected account configuration from channel command surfaces.

Workarounds

Upgrade to 2026.3.11 or later.

This is an account-scoped policy bypass inside a single gateway deployment. Channel commands such as /config set channels.<provider>.accounts.<id>... and config-backed /allowlist ... --config --account <id> could modify protected sibling-account configuration.

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

GHSA-8JHH-JCQG-MJ5P has a CVSS score of 6.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.3.11); upgrading removes the vulnerable code path.

Kodem intelligence

OpenClaw now authorizes config mutations against both the origin scope and each resolved target scope, and it rejects ambiguous root and collection writes from channel commands unless the caller is an internal gateway client with operator.admin. The fix shipped in [email protected].

1. What is GHSA-8JHH-JCQG-MJ5P? GHSA-8JHH-JCQG-MJ5P is a medium-severity missing authorization vulnerability in openclaw (npm), affecting versions < 2026.3.11. It is fixed in 2026.3.11. The application does not perform an authorization check before performing a sensitive operation.
2. How severe is GHSA-8JHH-JCQG-MJ5P? GHSA-8JHH-JCQG-MJ5P has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of openclaw are affected by GHSA-8JHH-JCQG-MJ5P? openclaw (npm) versions < 2026.3.11 is affected.
4. Is there a fix for GHSA-8JHH-JCQG-MJ5P? Yes. GHSA-8JHH-JCQG-MJ5P is fixed in 2026.3.11. Upgrade to this version or later.
5. Is GHSA-8JHH-JCQG-MJ5P exploitable, and should I be worried? Whether GHSA-8JHH-JCQG-MJ5P 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
6. What actually determines whether GHSA-8JHH-JCQG-MJ5P 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.
7. How do I fix GHSA-8JHH-JCQG-MJ5P? Upgrade openclaw to 2026.3.11 or later.