Security readout for executives and security teams
Plain-English summary
OpenClaw installations using the QQBot exec approvals feature may let a lower-trust user perform actions they should not be allowed to perform. The reported impact is broad: confidentiality, integrity, and availability can all be affected when the feature is enabled and reachable.
Executive priority
Prioritize within the next remediation cycle, sooner for internet-reachable or automation-heavy deployments. The business concern is unauthorized operational control, not just data disclosure.
Technical view
CVE-2026-62217 is a CWE-863 authorization flaw in OpenClaw exec approvals for QQBot. Sources describe affected exposure as OpenClaw 2026.5.14-beta.1 before 2026.5.27, with network access, low privileges, and no user interaction required. CVSS is 8.8 high.
Likely exposure
Exposure is most likely where OpenClaw beta deployments enabled QQBot exec approvals and made that path reachable to lower-trust callers or untrusted input sources.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Treat it as high-risk because the attack path is network reachable, low-complexity, and affects privileged operations.
Researcher notes
Evidence is limited to the supplied CVE, GitHub advisory, and VulnCheck reference metadata. There is a version-status inconsistency: narrative says before 2026.5.27, while affected data lists 2026.5.27. Validate directly against vendor guidance.
Mitigation direction
- Upgrade away from affected OpenClaw versions per vendor guidance.
- Disable QQBot exec approvals until version and configuration are verified.
- Restrict QQBot and approval endpoints to trusted networks or callers.
- Review allowlists and sender authorization rules for unexpected entries.
- Check GitHub advisory before assuming 2026.5.27 fully resolves exposure.
Validation and detection
- Inventory OpenClaw versions across production and beta environments.
- Confirm whether QQBot exec approvals are enabled or reachable.
- Review logs for non-allowlisted senders invoking approval-related operations.
- Verify authorization tests block lower-trust callers from exec approval paths.
- Confirm deployed version status against the vendor advisory.
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 lookupCVE-2026-62217 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:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
7.7HighVector: CVSS:4.0/AV:N/AC:L/AT:P/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-7jx6-764p-fgg9)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: OpenClaw 2026.5.14-beta.1 < 2026.5.27 Authentication Bypass via exec approvalsCVE 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.