## 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...
Full CISO analysis pending enrichment.
Affected Systems
| Package | Ecosystem | Vulnerable Range | Patched |
|---|---|---|---|
| openclaw | npm | < 2026.4.12 | 2026.4.12 |
Do you use openclaw? You're affected.
Severity & Risk
Recommended Action
Patch available
Update openclaw to version 2026.4.12
Compliance Impact
Compliance analysis pending. Sign in for full compliance mapping when available.
Frequently Asked Questions
What is GHSA-2767-2q9v-9326?
OpenClaw: QQBot reply media URL handling could trigger SSRF and re-upload fetched bytes
Is GHSA-2767-2q9v-9326 actively exploited?
No confirmed active exploitation of GHSA-2767-2q9v-9326 has been reported, but organizations should still patch proactively.
How to fix GHSA-2767-2q9v-9326?
Update to patched version: openclaw 2026.4.12.
What is the CVSS score for GHSA-2767-2q9v-9326?
No CVSS score has been assigned yet.
Technical Details
NVD Description
## 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 `openclaw@2026.4.14` includes the fix. ## Fix Commit(s) - `08ae021d1f4f02e0ca5fd8a3b9659291c1ecf95a` - `ddb7a8dd80b8d5dd04aafa44ce7a4354b568bb2d` - 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.
Weaknesses (CWE)
References
- github.com/advisories/GHSA-2767-2q9v-9326
- github.com/openclaw/openclaw/commit/08ae021d1f42905a85a550813c0d95169b171a6c
- github.com/openclaw/openclaw/commit/ddb7a8dd80b8d5dd04aafa44ce7a4354b568bb2d
- github.com/openclaw/openclaw/pull/63495
- github.com/openclaw/openclaw/pull/65788
- github.com/openclaw/openclaw/security/advisories/GHSA-2767-2q9v-9326
Timeline
Related Vulnerabilities
CVE-2026-30741 9.8 OpenClaw: RCE via request-side prompt injection
Same package: openclaw CVE-2026-28451 9.3 OpenClaw: SSRF via Feishu extension exposes internal services
Same package: openclaw GHSA-m3mh-3mpg-37hw 8.6 OpenClaw: .npmrc hijack enables RCE on plugin install
Same package: openclaw CVE-2026-27001 7.8 OpenClaw: prompt injection via unsanitized workspace path
Same package: openclaw GHSA-hr5v-j9h9-xjhg 7.7 OpenClaw: sandbox escape via mediaUrl path traversal
Same package: openclaw
AI Threat Alert