Executive brief
OpenClaw, an automation and browser orchestration tool, contains a security flaw in how it handles browser profile creation. In certain high-security configurations, an attacker with basic user access can force the server to make unauthorized requests to internal network resources or cloud metadata services. This could allow an attacker to probe private infrastructure that should otherwise be protected by the system's security policies.
Technical details
A Server-Side Request Forgery (SSRF) vulnerability exists in OpenClaw's browser Chrome DevTools Protocol (CDP) profile creation logic. The application normalized 'cdpUrl' values but failed to apply configured SSRF policies during the persistence phase. This allows an authenticated attacker to create stored profiles pointing to restricted private-network or cloud metadata endpoints. These endpoints are subsequently probed during routine profile status checks, effectively bypassing 'strict-mode' SSRF protections. The issue is resolved in version 2026.4.20 by enforcing policy checks during both profile creation and reachability operations.
Affected products
- OpenClaw openclaw < 2026.4.20
Timeline
- 2026-04-18: patched: Fix commits pushed to GitHub repository.
- 2026-04-21: advisory: GitHub Security Advisory GHSA-j4c5-89f5-f3pm published.
- 2026-05-11: disclosed: CVE-2026-45000 published.
References
- https://github.com/openclaw/openclaw/commit/1fd049e3074cac72f6734a7fe88468c84f5f8bd7
- https://github.com/openclaw/openclaw/commit/e90c89cf8b1459f2aa1f3a665be67392b6c03fdf
- https://github.com/openclaw/openclaw/security/advisories/GHSA-j4c5-89f5-f3pm
- https://www.vulncheck.com/advisories/openclaw-server-side-request-forgery-via-browser-cdp-profile-creation