Security readout for executives and security teams
Plain-English summary
OpenClaw has a high-severity authorization flaw where a lower-privileged authenticated operator can use agent runs to reach owner-only controls. In affected scoped-token deployments, this could let someone change sensitive control-plane behavior beyond their intended role.
Executive priority
Prioritize remediation for internet-accessible or shared OpenClaw deployments. The issue can affect confidentiality, integrity, and availability of control-plane functions, but current sources do not confirm active exploitation.
Technical view
Versions before OpenClaw 2026.3.1 have a CWE-863 authorization mismatch in agent execution. Authenticated callers with operator.write scope can invoke owner-only tool surfaces, including gateway and cron, because owner-only gating is inconsistently enforced during agent runs.
Likely exposure
Exposure is likely limited to organizations running OpenClaw before 2026.3.1 with scoped-token deployments and accounts or tokens holding operator.write scope.
Exploitation context
The source bundle reports network-accessible, low-complexity exploitation requiring low privileges and no user interaction. It does not state active exploitation, and KEV is false.
Researcher notes
Focus review on agent-run authorization flow and scoped-token enforcement. Evidence names gateway and cron as owner-only surfaces reachable through the mismatch; do not assume other products or surfaces without vendor confirmation.
Mitigation direction
- Upgrade OpenClaw to 2026.3.1 or a vendor-supported later release.
- Restrict operator.write scope to trusted identities only.
- Review scoped-token deployments for owner-only tool access assumptions.
- Audit recent agent runs involving gateway or cron surfaces.
- Check the vendor advisory for any additional compensating controls.
Validation and detection
- Confirm all OpenClaw instances report version 2026.3.1 or later.
- Inventory tokens and users with operator.write scope.
- Review logs for operator.write agent runs invoking owner-only surfaces.
- Test authorization boundaries in a non-production environment after patching.
- Verify gateway and cron actions require owner-level authorization.
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-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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 lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program 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-32051 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
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
8.7HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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-jr6x-2q95-fh2g)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: OpenClaw < 2026.3.1 - Authorization Bypass in Agent Runs via Owner-Only Tool AccessCVE 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.
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.