Security readout for executives and security teams
Plain-English summary
A flaw in OpenClaw lets a user who has legitimate access to one account change settings on other accounts that were supposed to be locked from writes. In practice, a low-privileged insider or a compromised account holder could quietly reconfigure sibling accounts, undermining trust boundaries between tenants and any protections built on the configWrites restriction.
Executive priority
Prioritize patching this quarter, especially where OpenClaw separates customer or business-unit accounts. The bug does not leak data directly, but it lets one account tamper with another's configuration, which can undermine tenant isolation and compliance assurances. No known exploitation reduces urgency slightly, but the fix is available and should be scheduled promptly.
Technical view
OpenClaw before 2026.3.11 fails to enforce the configWrites: false policy at the channel-command layer. Authenticated users can issue channel commands targeting `channels.<provider>.accounts.<id>` paths to mutate configuration on sibling accounts. This is a CWE-639 insecure direct object reference/authorization bypass with CVSS 4.0 7.1 (AV:N/AC:L/PR:L, high integrity impact). Fixed in 2026.3.11 per the vendor GHSA.
Likely exposure
Any OpenClaw deployment before 2026.3.11 that hosts multiple accounts or tenants and relies on configWrites: false to prevent cross-account configuration changes. Exposure grows where low-privileged users or automation tokens can invoke channel commands, especially in multi-tenant SaaS-style setups or shared internal environments.
Exploitation context
No public evidence of active exploitation and the CVE is not listed in CISA KEV. The GitHub Security Advisory and VulnCheck advisory describe the bypass but do not report in-the-wild abuse. Exploitation requires an authenticated account on the instance, so exposure is scoped to insiders or attackers who already hold valid credentials.
Researcher notes
CWE-639 authorization bypass rooted in command routing not honoring per-account configWrites. Vector shows PR:L and VI:H only — no confidentiality or availability impact per NVD-style scoring. Worth checking whether related channel command paths (users, integrations, secrets) share the same authorization gap, since one missed check often signals a broader pattern. Validate fix by attempting policy-bypassed writes against a lab sibling account after upgrade.
Mitigation direction
- Upgrade OpenClaw to 2026.3.11 or later across all environments.
- Restrict who can issue channel `/config set` commands until patched.
- Audit account permissions and remove unused or over-privileged users.
- Follow vendor guidance in GHSA-8jhh-jcqg-mj5p for interim controls.
- Rotate credentials for accounts that could have abused the bypass.
Validation and detection
- Confirm OpenClaw version is 2026.3.11 or higher on all nodes.
- Review logs for `/config set channels.*.accounts.*` commands crossing account boundaries.
- Test that configWrites: false on a sibling account now rejects channel-command writes.
- Inventory multi-account tenants and verify configuration integrity post-upgrade.
- Re-check ACLs on channel command endpoints against the fixed release notes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-32976 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.1 (4.0)
- Known Exploited
- No
- Published
Vector: 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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest 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——VulnCheckCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N2.83.6VulnCheckVulnerability scoring details
Base CVSS 4.0 score
7.1HighVector: 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
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitHub Security Advisory (GHSA-8jhh-jcqg-mj5p)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: OpenClaw < 2026.3.11 - Account-Scoped configWrites Policy Bypass via Channel CommandsCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.