Security readout for executives and security teams
Plain-English summary
OpenClaw versions before 2026.2.17 may leave session transcript files readable by local users. Those JSONL transcripts can contain sensitive tool output, including secrets. The main business risk is disclosure of credentials or operational data on systems where multiple users or processes can access the same host.
Executive priority
Treat this as high priority for developer and automation environments because transcript files may expose reusable secrets. Prioritize shared hosts and systems processing production credentials.
Technical view
This is a CWE-378 insufficient file permissions issue affecting OpenClaw before 2026.2.17. Session transcript JSONL files are created with overly broad default permissions, allowing local users to read transcript contents. The source CVSS is 8.4, local attack vector, low complexity, no user interaction.
Likely exposure
Exposure is most likely where OpenClaw before 2026.2.17 ran on shared workstations, servers, CI hosts, or developer systems and stored transcripts containing secrets or sensitive output.
Exploitation context
The bundle marks KEV as false and provides no evidence of active exploitation. Exploitation requires local access to a host containing affected transcript files.
Researcher notes
Sources do not provide exploit code or active exploitation evidence. The key validation question is whether affected transcript files exist and are readable by unintended local users. CVSS includes high confidentiality, integrity, and availability impact, but the described mechanism is transcript disclosure.
Mitigation direction
- Upgrade OpenClaw to 2026.2.17 or later.
- Review vendor advisory and patch notes for official remediation details.
- Restrict access to existing transcript files until remediated.
- Review exposed transcripts for secrets and rotate any affected credentials.
- Reduce unnecessary local user access on systems running OpenClaw.
Validation and detection
- Inventory OpenClaw installations and confirm versions before 2026.2.17.
- Identify hosts where OpenClaw session transcripts were written.
- Check transcript file permissions against vendor-fixed behavior.
- Review whether transcript contents include credentials or sensitive tool output.
- Confirm upgraded installations no longer create broadly readable transcripts.
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-378: 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 lookupCVE-2026-33572 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.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/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:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H2.55.9VulnCheckCVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
6.8MediumVector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Base CVSS 3.1 score
8.4HighVector: CVSS:3.1/AV:L/AC:L/PR:N/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-vr7j-g7jv-h5mp)CVE reference, VulnCheck · vendor-advisory
- Patch CommitCVE reference, VulnCheck · patch
- VulnCheck Advisory: OpenClaw < 2026.2.17 - Insufficient File Permissions in Session Transcript FilesCVE 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.
Creation of Temporary File With Insecure Permissions
Creation of Temporary File With Insecure Permissions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.