N/A

CVSS Score

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

GHSA-vr7j-g7jv-h5mp

GHSA-vr7j-g7jv-h5mp: 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)

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: 0o600
src/config/sessions/sessions.test.ts:303 includes regression coverage asserting 0o600

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.

(GitHub Advisory)

Miggo Vulnerability Database

→

GHSA-vr7j-g7jv-h5mp

GHSA-vr7j-g7jv-h5mp:

N/A

CVSS Score

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
openclaw	npm	<= 2026.2.15	2026.2.17

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability lies in the creation of session transcript files with default permissions, which could be overly permissive depending on the system's umask. This could allow local users to access sensitive information within these transcript files. The analysis of the provided patch 095d522099653367e1b76fa5bb09d4ddf7c8a57c reveals the exact locations where this vulnerability is addressed.

Two functions were identified as being responsible for creating these files:

ensureSessionHeader in src/config/sessions/transcript.ts
ensureTranscriptFile in src/gateway/server-methods/chat.ts

In both functions, the patch modifies the file-writing operation (fs.promises.writeFile and fs.writeFileSync) to explicitly set the file mode to 0o600 (read/write for the owner only). This ensures that newly created transcript files are always created with secure permissions, regardless of the system's umask setting.

The functions ensureSessionHeader and ensureTranscriptFile are therefore the vulnerable functions, as they are directly responsible for the insecure file creation. During exploitation, a call to either of these functions would result in the creation of a transcript file with potentially insecure permissions.

Vulnerable functions

ensureSessionHeader

src/config/sessions/transcript.ts

This function writes the session header to a file without explicitly setting file permissions. This results in the file being created with default system permissions, which may be too permissive, allowing unauthorized users to read sensitive session data.

ensureTranscriptFile

src/gateway/server-methods/chat.ts

This function writes the transcript file without explicitly setting file permissions. This results in the file being created with default system permissions, which may be too permissive, allowing unauthorized users to read sensitive session data.

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.