Summary
OpenClaw: Browser CDP profile creation skipped strict-mode SSRF checks
Affected Packages / Versions
- Package:
openclaw(npm) - Affected versions:
< 2026.4.20 - Patched version:
2026.4.20
Release
Fixed in OpenClaw 2026.4.20.
Impact
Browser profile creation normalized cdpUrl values before persisting them, but did not apply the configured browser SSRF policy at creation time. In deployments that explicitly disabled private-network CDP targets, a stored profile could still point at a private-network or metadata endpoint and later be probed by normal profile status flows.
Default trusted-operator browser behavior allows private-network CDP endpoints, so this only affected strict-mode deployments. Severity is low.
Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
OpenClaw now checks CDP endpoints against the browser SSRF policy during profile creation and reachability operations.
Fix commits:
1fd049e3074cac72f6734a7fe88468c84f5f8bd7e90c89cf8b1459f2aa1f3a665be67392b6c03fdf
Frequently Asked Questions
- What is GHSA-J4C5-89F5-F3PM? GHSA-J4C5-89F5-F3PM is a low-severity server-side request forgery (SSRF) vulnerability in openclaw (npm), affecting versions < 2026.4.20. It is fixed in 2026.4.20. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
- Which versions of openclaw are affected by GHSA-J4C5-89F5-F3PM? openclaw (npm) versions < 2026.4.20 is affected.
- Is there a fix for GHSA-J4C5-89F5-F3PM? Yes. GHSA-J4C5-89F5-F3PM is fixed in 2026.4.20. Upgrade to this version or later.
- Is GHSA-J4C5-89F5-F3PM exploitable, and should I be worried? Whether GHSA-J4C5-89F5-F3PM is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-J4C5-89F5-F3PM is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-J4C5-89F5-F3PM? Upgrade
openclawto 2026.4.20 or later.