GHSA-c9h3-5p7r-mrjh is a high-severity (CVSS 7.7) vulnerability in openclaw. O3 Security confirms whether GHSA-c9h3-5p7r-mrjh is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
OpenClaw: Discord event cover images bypassed sandbox media normalization
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
openclawnpmDescription
Summary
Discord event cover images bypassed sandbox media normalization.
Affected Packages / Versions
- Package:
openclaw - Ecosystem: npm
- Affected versions:
>= 2026.4.7 < 2026.4.10 - Patched versions:
>= 2026.4.10
Impact
Discord event cover image parameters could bypass the sandbox media normalization path used for outbound local media, allowing host-local media references to reach a channel action path that expected normalized media.
Technical Details
The fix includes Discord eventCreate.image in sandbox media normalization and adds coverage for the event-create media path.
Fix
The issue was fixed in #64377. The first stable tag containing the fix is v2026.4.10, and [email protected] includes the fix.
Fix Commit(s)
979c6f09d6fad96596feb91c905934be7e0b4f15- PR: #64377
Release Process Note
Users should upgrade to openclaw 2026.4.10 or newer. The latest npm release, 2026.4.14, already includes the fix.
Credits
Thanks to @zsxsoft, with sponsorship from @KeenSecurityLab and @qclawer for reporting this issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | openclaw | ≥ 2026.4.7&&< 2026.4.10 | 2026.4.10 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update openclaw to 2026.4.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c9h3-5p7r-mrjh 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 pinpoints whether GHSA-c9h3-5p7r-mrjh is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-c9h3-5p7r-mrjh. 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-c9h3-5p7r-mrjh in your dependencies?
O3 detects GHSA-c9h3-5p7r-mrjh across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.