Summary
OpenClaw session transcript files were created without forced user-only permissions
openclaw created new session transcript JSONL files with overly broad default permissions in affected releases. On multi-user hosts, other local users or processes could read transcript contents, including secrets that might appear in tool output.
Affected Packages / Versions
- Package:
openclaw(npm) - Affected versions:
<= 2026.2.15 - First fixed version:
2026.2.17 - Current latest npm release checked during verification:
2026.3.13(not affected)
Fix Commit(s)
095d522099653367e1b76fa5bb09d4ddf7c8a57c
Release Note
This fix first shipped in 2026.2.17 and is present in the current npm release 2026.3.13.
Impact
Session transcript JSONL files are created under the local OpenClaw session store. In affected releases, newly created transcript files did not force user-only permissions, so transcript contents could be readable by other local users depending on the host environment and umask behavior.
A file, directory, or other resource is assigned permissions that allow broader access than intended. Typical impact: unauthorized read, modification, or execution of the resource.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
New transcript files are now created with 0o600 permissions. Existing transcript permission drift is also remediated by the security audit fix flow.
Verified in code:
src/config/sessions/transcript.ts:82writes new transcript files withmode: 0o600src/config/sessions/sessions.test.ts:303includes regression coverage asserting0o600
Frequently Asked Questions
- What is CVE-2026-33572? CVE-2026-33572 is a medium-severity incorrect permission assignment for critical resource vulnerability in openclaw (npm), affecting versions <= 2026.2.15. It is fixed in 2026.2.17. A file, directory, or other resource is assigned permissions that allow broader access than intended.
- Which versions of openclaw are affected by CVE-2026-33572? openclaw (npm) versions <= 2026.2.15 is affected.
- Is there a fix for CVE-2026-33572? Yes. CVE-2026-33572 is fixed in 2026.2.17. Upgrade to this version or later.
- Is CVE-2026-33572 exploitable, and should I be worried? Whether CVE-2026-33572 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-33572 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-33572? Upgrade
openclawto 2026.2.17 or later.