GHSA-2767-2q9v-9326 is a high-severity (CVSS 8.2) vulnerability in openclaw. O3 Security confirms whether GHSA-2767-2q9v-9326 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
OpenClaw: QQBot reply media URL handling could trigger SSRF and re-upload fetched bytes
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
QQBot reply media URL handling could trigger SSRF and re-upload fetched bytes.
Affected Packages / Versions
- Package:
openclaw - Ecosystem: npm
- Affected versions:
< 2026.4.12 - Patched versions:
>= 2026.4.12
Impact
QQBot reply media URLs could be treated as trusted media sources, allowing SSRF fetches whose returned bytes were then re-uploaded through the channel.
Technical Details
The fix routes QQBot remote media fetches through SSRF-guarded media fetching and explicit URL allowlist policy.
Fix
The issue was fixed in #63495 and #65788. The first stable tag containing the fix is v2026.4.12, and [email protected] includes the fix.
Fix Commit(s)
08ae021d1f4f02e0ca5fd8a3b9659291c1ecf95addb7a8dd80b8d5dd04aafa44ce7a4354b568bb2d- PR: #63495, #65788
Release Process Note
Users should upgrade to openclaw 2026.4.12 or newer. The latest npm release, 2026.4.14, already includes the fix.
Credits
Thanks to @threalwinky for reporting this issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | openclaw | all versions | 2026.4.12 |
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.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2767-2q9v-9326 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-2767-2q9v-9326 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-2767-2q9v-9326. 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-2767-2q9v-9326 in your dependencies?
O3 detects GHSA-2767-2q9v-9326 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.