CVE-2026-35629: SSRF in openclaw Node.js Package

The SSRF vulnerability in openclaw allows an attacker to craft malicious requests that originate from the server itself, bypassing normal network security controls. This can lead to unauthorized access to internal services, data, or resources that are not directly accessible from the outside world. An attacker could potentially scan internal networks, access sensitive configuration files, or even interact with internal APIs. The impact is amplified by the fact that this vulnerability is an incomplete fix for CVE-2026-28476, suggesting that other SSRF vectors might still exist within the package.

1. Reserved2026-04-04
2. Published2026-03-29
3. Modified2026-04-10
4. EPSS updated2026-04-17

The primary mitigation for CVE-2026-35629 is to immediately upgrade the openclaw package to version 2026.3.28 or later. If upgrading is not immediately feasible due to compatibility issues or breaking changes, consider implementing a Web Application Firewall (WAF) or proxy to filter outbound requests and block those targeting internal resources. Specifically, configure the WAF to deny requests with internal IP addresses or those attempting to access sensitive internal endpoints. Additionally, review and restrict the configured base URLs within the openclaw package to only allow trusted and necessary domains. After upgrading, confirm the fix by attempting to trigger the SSRF vulnerability with a known malicious URL and verifying that the request is blocked.