Security readout for executives and security teams
Plain-English summary
OpenClaw before 2026.3.11 can let an approved script become a different script before it runs. That breaks the approval control and may let an attacker execute unintended code as the OpenClaw runtime user.
Executive priority
Treat this as a high-priority integrity issue if OpenClaw automates privileged local workflows. Patch exposed deployments promptly and review approval controls before relying on them for security decisions.
Technical view
The issue is a CWE-367 time-of-check/time-of-use approval integrity flaw in node-host approval. When exact file binding cannot occur, scripts can be modified between approval and execution, allowing rewritten local code to run with OpenClaw runtime privileges.
Likely exposure
Exposure is likely limited to OpenClaw deployments before 2026.3.11 using node-host approval workflows where attackers can modify approved local scripts before execution.
Exploitation context
The bundle does not show CISA KEV listing or confirmed active exploitation. The advisory describes attacker-controlled script replacement after approval, requiring privileges and user interaction per the CVSS vector.
Researcher notes
The key condition is failure to bind approval to the exact file executed. Validate race or replacement opportunities without publishing exploit procedure. Evidence in the bundle supports high impact but not public exploitation.
Mitigation direction
- Upgrade OpenClaw to 2026.3.11 or later, per vendor guidance.
- Review the GitHub advisory for any additional vendor-specific remediation notes.
- Restrict who can modify scripts used by node-host approval workflows.
- Temporarily avoid approval flows where script identity cannot be strongly bound.
Validation and detection
- Inventory OpenClaw instances and identify versions earlier than 2026.3.11.
- Find node-host approval workflows that execute local scripts.
- Check whether approved scripts can be modified before execution.
- Review recent approvals for script changes between approval and runtime.
- Confirm remediation by retesting approval-to-execution script integrity.
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-367: 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-32979 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.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H1.35.9VulnCheckCVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
7HighVector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Base CVSS 3.1 score
7.3HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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-xf99-j42q-5w5p)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: OpenClaw < 2026.3.11 - Unbound Interpreter and Runtime Commands Bypass in node-host ApprovalCVE 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.
Time-of-check Time-of-use (TOCTOU) Race Condition
Time-of-check Time-of-use (TOCTOU) Race Condition represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.