Security readout for executives and security teams
Plain-English summary
This is a low-severity approval bypass in OpenClaw before 2026.2.26. In specific approval-enabled workflows, someone who already has an approval id could reuse it while changing environment input. The likely business impact is limited integrity risk in automated execution workflows, not data theft or service outage based on the provided CVSS vector.
Executive priority
Treat this as a targeted workflow-integrity issue, not an emergency internet-wide exposure. Prioritize upgrade during the next normal security maintenance window, sooner if OpenClaw controls sensitive automation or privileged operational tasks.
Technical view
CVE-2026-32058 is a CWE-863 authorization weakness in OpenClaw system.run flows using host=node. Approved execution context was not sufficiently bound to environment variables, allowing modified env input with a reused approval id. The CVSS 3.1 score is 2.6, with low integrity impact, high attack complexity, required privileges, and user interaction.
Likely exposure
Exposure is likely limited to OpenClaw deployments before 2026.2.26 that use approval-enabled system.run workflows with host=node. Risk increases where approval ids are visible to lower-privileged users, logs, integrations, or shared workflow state.
Exploitation context
The source bundle does not indicate active exploitation, and KEV is false. Exploitation requires access to an approval id, prior approval context, privileges, and user interaction. The described impact is bypassing execution-integrity controls through modified environment variables, not direct code execution from an unauthenticated position.
Researcher notes
The available evidence identifies affected versions, class, vector, and patch reference, but not detailed exploit telemetry. Focus review on approval context binding, env input integrity, approval id handling, and regression coverage around host=node execution flows.
Mitigation direction
- Upgrade OpenClaw to 2026.2.26 or later.
- Review the GitHub advisory and patch commit for vendor-specific remediation details.
- Restrict access to approval ids in logs, workflow output, and integrations.
- Review approval-enabled system.run workflows that use host=node.
- Reissue or invalidate outstanding approvals after applying the vendor fix.
Validation and detection
- Inventory OpenClaw versions and flag instances older than 2026.2.26.
- Identify workflows using system.run with host=node and approval enforcement.
- Check whether approval ids are exposed in logs, tickets, chat, or CI output.
- Confirm upgraded deployments include the vendor patch behavior.
- Review recent workflow history for unexpected environment input changes.
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 lookupCVE-2026-32058 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
- Low
- CVSS
- 2.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:L/A: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:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:L/A:N1.21.4VulnCheckCVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
2LowVector: CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
Base CVSS 3.1 score
2.6LowVector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:L/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-hjvp-qhm6-wrh2)CVE reference, VulnCheck · vendor-advisory
- Patch CommitCVE reference, VulnCheck · patch
- VulnCheck Advisory: OpenClaw < 2026.2.26 - Approval Context-Binding Weakness in system.run via host=nodeCVE 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.