CVE-2026-33572: OpenClaw session transcript files were created without forced user-only permissions
OpenClaw up to and including 2026.2.15 created new session transcript JSONL files without forcing user-only permissions. On a multi-user host, other local users or processes could read the transcripts, which can contain secrets from tool output. The first fixed version is 2026.2.17, which writes new files with mode 0o600.
Published Mar 16, 2026 · Updated Apr 6, 2026 · Analysis Oct 31, 2026
What an attacker can do
OpenClaw keeps each session as a JSONL transcript in its local session store. Affected releases created these files with the process default mode, so the umask of the host decided who could read them. Where the umask allowed group or world read, any other account on the machine could open the files (CWE-276, CWE-732).
A transcript records the whole session, including the output of tools the agent ran. That output can hold API keys, tokens, file contents, command results and private messages. The attacker needs a local account or a process on the same host, which matches the local attack vector and low privilege requirement in the CVSS data.
This mostly matters on shared servers, build hosts, jump boxes and lab machines where several people log in. On a single-user laptop the exposure is small. The flaw is a read of data, with no write or code execution. Fixing permissions does not remove copies another user already made.
Who is affected
The npm package openclaw up to and including 2026.2.15. Versions 2026.2.17 and later are fixed, and the advisory says 2026.3.13 is not affected. Check the version:
npm ls -g openclaw
openclaw --versionThen look at the permissions of existing transcript .jsonl files in your session directory, next to sessions.json. Files that are readable by group or others were exposed.
openclaw
- Ecosystem
- npm
- Affected
- <= 2026.2.15
- Fixed in
- 2026.2.17
- Check
npm ls openclaw
How to fix it
Upgrade to 2026.2.17 or later:
npm install -g openclaw@latestNew transcripts are then created with mode 0o600. The commit also makes the security audit fix flow set 0o600 on existing .jsonl files in the sessions directory:
openclaw security audit --fixIf the host was shared while the old version ran, treat secrets that appeared in earlier sessions as exposed, and rotate them.
How to tell if you were hit
List the transcript files and check their modes. Any .jsonl file in the sessions directory that is not 600 was readable beyond its owner. Review file access audit logs, if enabled, for reads of these files by other accounts. The sources name no other indicator, and a plain read leaves no trace without auditing.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
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)
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.
Fix
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
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.
Credited to hsongkai11.
Questions
- Which OpenClaw version fixed CVE-2026-33572?
2026.2.17 was the first fixed version. Versions up to and including 2026.2.15 are affected.
- Does upgrading fix transcripts that already exist?
New files get 0o600 automatically. For existing ones, run openclaw security audit --fix, which now sets 0o600 on .jsonl transcripts in the sessions directory.
- Is this exploitable remotely?
No. The attacker needs local access to the same host, as another user or process. The risk is highest on shared machines.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
More OpenClaw vulnerabilities
All OpenClaw entriesCVE-2026-62197
OpenClaw: Browser CDP discovery could accept blocked WebSocket URLs
medium8.5Oct 21, 2026CVE-2026-35630
OpenClaw: QQBot native approval buttons did not enforce configured approver identity
high8.0Jul 2, 2026CVE-2026-53806
OpenClaw: Combined POSIX shell options could confuse exec revalidation
high8.8Jul 2, 2026CVE-2026-53809
OpenClaw: Embedded runner policy could be confused by provider aliases
medium3.8Jul 2, 2026CVE-2026-53810
OpenClaw's marketplace runtime extension metadata could point at unscanned payloads
high8.8Jul 2, 2026CVE-2026-53811
OpenClaw: Matrix allowFrom could bind to mutable display names
high8.8Jul 2, 2026
