SSRF Vulnerability in OpenClaw QQ Bot Extension: Inadequate Media Fetch Protection
Summary
GHSA-3fv3-6p2v-gxwj: OpenClaw QQ Bot Extension missing SSRF Protection on All Media Fetch Paths. Affects openclaw versions < 2026.4.8. Fixed in 2026.4.8. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
OpenClaw is a user-controlled local assistant designed to enhance user productivity by integrating various functionalities, including a QQ Bot Extension that allows users to interact with QQ services. The package is available via npm and is widely used for its ease of use and flexibility. However, it has been identified that the QQ Bot Extension lacks sufficient Server-Side Request Forgery (SSRF) protection on its media fetch paths, which poses a security risk.
Vulnerability Detail
The vulnerability arises from the QQ Bot Extension's failure to consistently route media download paths through the SSRF guard and allowlist policy. This oversight can lead to unauthorized access to internal services or sensitive data, as attackers could exploit this weakness to send crafted requests to internal systems. The issue is particularly concerning within the OpenClaw trust model, which does not assume a multi-tenant service boundary, potentially exposing users to significant risks.
How To Fix
Latest published version: 2026.10.6 as of 22 Oct 2026
npm install openclaw@2026.10.6Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
2026.4.8
This is the first release that contains the fix.
npm install openclaw@2026.4.8Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a temporary measure, users can implement additional validation on media fetch requests to ensure they do not point to internal resources. However, the best course of action is to update to the patched version.
Conclusion
The OpenClaw QQ Bot Extension has a significant SSRF vulnerability that can expose users to various security risks. It is crucial to update to the patched version 2026.4.8 to mitigate these risks effectively. Users are encouraged to utilize tools like Vulert to monitor their applications for vulnerabilities and ensure their software remains secure.
See every vulnerability recorded for openclaw →
FAQ
Server-Side Request Forgery (SSRF) is a vulnerability that allows an attacker to send crafted requests from a vulnerable server to internal or external resources. It is a concern because it can lead to unauthorized access to sensitive data or services.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By simply using your package-lock.json file, you can check for vulnerabilities without needing to access the code. Visit the Vulert playground at Vulert Scanner for more information.
Failure to address this vulnerability could lead to unauthorized access to internal services, data breaches, and potential exploitation by malicious actors, compromising the security of your application.
While the best solution is to update to the patched version, you can implement additional validation on media fetch requests to prevent them from targeting internal resources as a temporary workaround.
The CVSS score for this vulnerability is 5.9, indicating a moderate level of risk associated with its exploitation.
References
Related vulnerabilities
Recent vulnerabilities recorded for openclaw.
Follow Vulert in Google
Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.