CVE-2026-41302
Server-Side Request Forgery in OpenClaw Marketplace Plugin
Publication date: 2026-04-21
Last updated on: 2026-04-27
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| openclaw | openclaw | to 2026.3.31 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-918 | The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-41302 is a Server-Side Request Forgery (SSRF) vulnerability affecting OpenClaw versions before 2026.3.31. It exists in the marketplace plugin download functionality due to unguarded fetch() calls. This flaw allows remote attackers to make arbitrary network requests from the affected system.
By exploiting this vulnerability, attackers can access internal resources or interact with external services on behalf of the vulnerable server, potentially bypassing network restrictions.
How can this vulnerability impact me? :
This vulnerability can allow attackers to make unauthorized network requests from your system, potentially accessing internal or restricted resources that should not be exposed externally.
Such unauthorized access could lead to information disclosure or interaction with external services in unintended ways, which might compromise the security or integrity of your network environment.
However, the CVSS scores indicate a medium severity with low impact on confidentiality and availability but some impact on integrity and a high scope change, meaning the vulnerability can affect components beyond the initially vulnerable one.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves unguarded fetch() calls in the marketplace plugin download functionality that allow arbitrary network requests. Detection can focus on monitoring or auditing network requests made by the OpenClaw server, especially those triggered by the marketplace plugin.
You can detect potential exploitation by inspecting outgoing HTTP requests from the OpenClaw server to unexpected or unauthorized internal or external URLs.
Suggested commands include using network monitoring tools or packet capture utilities such as:
- tcpdump or tshark to capture outgoing HTTP requests from the OpenClaw server, e.g., `tcpdump -i eth0 -A port 80 or port 443`
- Using curl or wget to manually test the marketplace plugin download endpoints for SSRF by attempting to inject URLs and observing server behavior.
- Reviewing application logs for unusual or unexpected URLs being fetched by the marketplace plugin.
Additionally, auditing the OpenClaw server's network requests with tools that can track or log fetch() calls or API calls related to the marketplace plugin may help detect exploitation attempts.
What immediate steps should I take to mitigate this vulnerability?
The primary mitigation step is to upgrade OpenClaw to version 2026.3.31 or later, where the vulnerability has been fixed.
The fix involves implementing SSRF guard policies that restrict network requests made by the marketplace plugin and Ollama plugin to validated and allowed hostnames, preventing arbitrary network requests.
If upgrading immediately is not possible, consider restricting outbound network access from the OpenClaw server to only trusted hosts and monitoring network traffic for suspicious requests.
Review and apply any patches or code changes related to SSRF protections, such as those described in the GitHub commit 8deb9522f3d2680820588b190adb4a2a52f3670b, which introduces hostname allowlisting and guarded fetch operations.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not explicitly address how the CVE-2026-41302 vulnerability impacts compliance with common standards and regulations such as GDPR or HIPAA.