OpenClaw: Discord event cover images bypassed sandbox media normalizationGHSA-c9h3-5p7r-mrjh
HIGHFix: openclaw/openclaw#64377GHSA-c9h3-5p7r-mrjh is a high-severity (CVSS 7.7) CWE-184 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- 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-c9h3-5p7r-mrjh.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
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
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.10npm install openclaw@2026.4.10 |
Affected Products
openclawopenclawDetection & 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.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.
Frequently Asked Questions
Is GHSA-c9h3-5p7r-mrjh in your dependencies?
Find it across npm, including transitive dependencies.