GitHub Advisoryadvisory · npm

GHSA-53vx-pmqw-863c OpenClaw: Browser SSRF policy default allowed private-network navigation

MEDIUM Published 2026-04-17 Modified 2026-05-08 Official page ↗
Aliases
CVE-2026-43527
Ecosystem
npm
Packages
openclaw
Severity
Moderate
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Weaknesses
CWE-1188, CWE-918
Reviewed
2026-04-17

Affected packages

• npm openclaw: < 2026.4.14 → fixed in 2026.4.14

Description

Summary Browser SSRF policy default allowed private-network navigation. Affected Packages / Versions • Package: `openclaw` • Ecosystem: npm • Affected versions: `= 2026.4.14` Impact Browser SSRF protection could allow private-network navigation by default in paths where restrictive behavior was expected, exposing internal services or metadata endpoints through browser-driven requests. Technical Details The fix preserves strict SSRF configuration semantics, keeps private-network access disabled unless explicitly opted in, and updates loopback CDP readiness handling for the stricter default. Fix The issue was fixed in #66354 and #66386. The first stable tag containing the fix is `v2026.4.14`, and `[email protected]` includes the fix. Fix Commit(s) • `024f4614a1a1831406e763adc40ef226e3d5e9ed` • `1dabfef28db523e7de81edeb3dd689e9171236a2` • `213c36cf51121ef6c05cfccd78037371f968f31a` • `7eecfa411df3d12e6b810e6ca5df47254fc3db3f` • PR: #66354, #66386 Release Process Note Users should upgrade to `openclaw` 2026.4.14 or newer. The latest npm release, `2026.4.14`, already includes the fix. Credits Thanks to @zsxsoft, with sponsorship from @KeenSecurityLab and @qclawer for reporting this issue.

Related

Alias · CVE (1)

  • CVE-2026-43527 OpenClaw before 2026.4.14 contains a server-side request forgery vulnerability in browser SSRF policy that allows private-network… vulnerability

Weakness · CWE (2)

  • CWE-1188 Initialization of a Resource with an Insecure Default weakness
  • CWE-918 Server-Side Request Forgery weakness

References