How severe is GHSA-vr7j-g7jv-h5mp?

No CVSS score has been assigned to GHSA-vr7j-g7jv-h5mp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-vr7j-g7jv-h5mp?

GHSA-vr7j-g7jv-h5mp affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-vr7j-g7jv-h5mp?

Update openclaw to 2026.2.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vr7j-g7jv-h5mp is resolved across your whole dependency graph.

How do I detect GHSA-vr7j-g7jv-h5mp in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-vr7j-g7jv-h5mp if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-vr7j-g7jv-h5mp?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-vr7j-g7jv-h5mp can be triaged on real exposure rather than presence alone.

Is GHSA-vr7j-g7jv-h5mp actively exploited in the wild?

No public exploit code has been indexed for GHSA-vr7j-g7jv-h5mp yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-vr7j-g7jv-h5mp?

GHSA-vr7j-g7jv-h5mp has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 6th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-vr7j-g7jv-h5mp?

GHSA-vr7j-g7jv-h5mp is classified as CWE-378 (CWE-378). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-vr7j-g7jv-h5mp published, and has it been updated?

GHSA-vr7j-g7jv-h5mp was published on March 16, 2026 and was last updated on April 6, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-vr7j-g7jv-h5mp — openclaw

Fix: openclaw/openclaw@095d522

GHSA-vr7j-g7jv-h5mp is a CWE-378 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw session transcript files were created without forced user-only permissions

Also known asCVE-2026-33572

Published

Mar 16, 2026

Updated

Apr 6, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 26, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs6th percentile — riskier than 6% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

133other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

openclawnpm

3.3Mdownloads / week

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.2.17`npm install openclaw@2026.2.17`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update openclaw to 2026.2.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vr7j-g7jv-h5mp is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-vr7j-g7jv-h5mp can be triaged on real exposure rather than presence alone.

Tailored to GHSA-vr7j-g7jv-h5mp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

`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

O3 Security · Impact-Aware SCA

Is GHSA-vr7j-g7jv-h5mp in your dependencies?

O3 Security finds GHSA-vr7j-g7jv-h5mp across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works