CVE-2026-33572
Openclaw ≤ 2026.2.17
Raw vector
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2026-33572 is a medium-severity Creation of Temporary File With Insecure Permissions (CWE-378) vulnerability in Openclaw Openclaw. Its CVSS base score is 6.8 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked at the 2th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-6 (Least Privilege) and SC-4 (Information in Shared System Resources) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-33572 affects OpenClaw versions prior to 2026.2.17, where the software creates session transcript files in JSONL format with overly broad default permissions. This misconfiguration, tied to CWE-378 (Creation of Temporary File With Insecure Permissions), enables unauthorized reading of these files by local users. The vulnerability carries a CVSS v3.1 base score of 8.4 (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), highlighting high confidentiality, integrity, and availability impacts from local exploitation.
Local attackers with access to the host system can exploit this issue without privileges by directly reading the transcript files, extracting sensitive information such as secrets captured in tool outputs during sessions. No user interaction or special conditions are required beyond local presence, making it feasible for malicious users on shared systems or compromised hosts to harvest credentials or other confidential data logged in transcripts.
Mitigation involves upgrading to OpenClaw 2026.2.17 or later, as detailed in the patching commit at https://github.com/openclaw/openclaw/commit/095d522099653367e1b76fa5bb09d4ddf7c8a57c. The GitHub security advisory (https://github.com/openclaw/openclaw/security/advisories/GHSA-vr7j-g7jv-h5mp) and VulnCheck analysis (https://www.vulncheck.com/advisories/openclaw-insufficient-file-permissions-in-session-transcript-files) recommend applying this fix promptly and reviewing permissions on existing transcript files to prevent unauthorized access.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-17024
Vulnerability Data
OpenClaw before 2026.2.17 creates session transcript JSONL files with overly broad default permissions, allowing local users to read transcript contents. Attackers with local access can read transcript files to extract sensitive information including secrets from tool output.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
AC-6 limits privileges granted to processes creating or accessing temporary files, reducing blast radius of insecure permissions.
SC-4 directly stops unauthorized information transfer through shared resources such as temporary files created with weak permissions.
AC-3 enforces access authorizations on system resources including files, structurally stopping insecure temporary file permissions from being exploitable.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require proper temporary-file creation and permission handling.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure coding standards directly prohibit insecure temporary file creation and permissions.
Security testing can detect insecure temporary files but does not prevent their creation.
Secure SDLC mandates secure handling of temporary files and permissions.
Application security requirements include secure creation and permissioning of temporary files.
Secure architecture principles require least-privilege file creation and access controls.
Information access restriction can limit exposure but does not address file creation itself.