GitHub Advisoryadvisory · npm

GHSA-j4c5-89f5-f3pm OpenClaw: Browser CDP profile creation skipped strict-mode SSRF checks

LOW Published 2026-04-25 Modified 2026-04-25 Official page ↗
Ecosystem
npm
Packages
openclaw
Severity
Low
CVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
Weaknesses
CWE-918
Reviewed
2026-04-25

Affected packages

• npm openclaw: < 2026.4.20 → fixed in 2026.4.20

Description

Affected Packages / Versions • Package: `openclaw` (npm) • Affected versions: `< 2026.4.20` • Patched version: `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. Fix OpenClaw now checks CDP endpoints against the browser SSRF policy during profile creation and reachability operations. Fix commits: • `1fd049e3074cac72f6734a7fe88468c84f5f8bd7` • `e90c89cf8b1459f2aa1f3a665be67392b6c03fdf` Release Fixed in OpenClaw `2026.4.20`.

Related

Weakness · CWE (1)

  • CWE-918 Server-Side Request Forgery weakness

References