openclaw
Affected
- introduced
0, fixed2026.2.17(semver)
Fixed versions
2026.2.17
Fix
- Fixed version
2026.2.17npm install [email protected]
Advisory
Also known as: CVE-2026-33572
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
openclaw (npm)<= 2026.2.152026.2.172026.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:82 writes new transcript files with mode: 0o600src/config/sessions/sessions.test.ts:303 includes regression coverage asserting 0o600Fix Commit(s)
095d522099653367e1b76fa5bb09d4ddf7c8a57cRelease Note
This fix first shipped in 2026.2.17 and is present in the current npm release 2026.3.13.
Medium Basis: The source's own band: MODERATE
0, fixed 2026.2.17 (semver)2026.2.17
2026.2.17npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0