GHSA-mr34-9552-qr95 is a medium-severity (CVSS 5.8) CWE-73 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.
OpenClaw: Webchat media embedding enforces local-root containment for tool-result files
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-mr34-9552-qr95.
EPSS Exploitation Probability
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.
How urgent is this, really
GHSA-mr34-9552-qr95 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
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.
openclawnpmDescription
Summary
Webchat tool-result media normalization could pass local and UNC-style file paths into the host-side media embedding path without applying the configured local-root containment policy.
Impact
A crafted tool-result media reference could cause the host to attempt local file reads or Windows UNC/network path access while preparing webchat media blocks. This could disclose allowed host files or trigger network credential exposure on affected Windows deployments. Severity remains medium because exploitation depends on a tool-result media path reaching the webchat embedding path, but the sink is a host-side file read before the user sees the rendered result.
Affected versions
- Affected:
>= 2026.4.7, < 2026.4.15 - Patched:
2026.4.15
Fix
OpenClaw 2026.4.15 hardens the webchat media path and the shared media resolver. Remote-host file:// URLs and Windows network paths are rejected before filesystem access, and audio embedding now enforces configured localRoots containment before stat or read operations.
Verified in v2026.4.15:
src/gateway/server-methods/chat-webchat-media.tsuses safe file-URL parsing, rejects Windows network paths, and callsassertLocalMediaAllowedbefore probing local audio files.src/media/web-media.tsrejects remote-hostfile://URLs, Windows network paths, and local-root bypasses on the shared media path.src/gateway/server-methods/chat-webchat-media.test.tscovers both remote-hostfile://rejection and local-root denial before filesystem access.
Fix commits included in v2026.4.15 and absent from v2026.4.14:
1470de5d3e0970856d86cd99336bb8ada3fe87davia PR #672936e58f1f9f54bca1fea1268ec0ee4c01a2af03ddevia PR #6729852ef42302ead9e183e6c8810e0a04ee4ef8ae9fcvia PR #67303 as defense-in-depth for trusted media passthrough anchoring
Thanks to @Kherrisan for reporting this issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | openclaw | ≥ 2026.4.7&&< 2026.4.15 | 2026.4.15npm install openclaw@2026.4.15 |
Detection & mitigation playbook
Open-source dependencyDetect
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.4.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mr34-9552-qr95 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-mr34-9552-qr95 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-mr34-9552-qr95. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-mr34-9552-qr95 in your dependencies?
O3 Security finds GHSA-mr34-9552-qr95 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.