6.3

CVSS Score

4.0

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

CVE-2026-43527

CVE-2026-43527: OpenClaw < 2026.4.14 - Server-Side Request Forgery via Private Network Navigation

OpenClaw before 2026.4.14 contains a server-side request forgery vulnerability in browser SSRF policy that allows private-network navigation by default. Attackers can exploit this misconfiguration to access internal services or metadata endpoints through browser-driven requests.

(GitHub Advisory)

Miggo Vulnerability Database

→

CVE-2026-43527

CVE-2026-43527:

6.3

CVSS Score

4.0

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
openclaw	npm	< 2026.4.14	2026.4.14

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability is a Server-Side Request Forgery (SSRF) in the openclaw npm package, caused by an insecure default SSRF policy for browser operations. The core of the issue lies in the resolveBrowserSsrFPolicy function, which was responsible for generating the SSRF policy. By default, it produced a permissive policy that allowed navigation to private networks.

This weak policy was then used by several functions that perform network requests, such as fetchCdpChecked, isChromeReachable, and getChromeWebSocketUrl. These functions are used for interacting with the Chrome DevTools Protocol (CDP) for browser automation. Because they inherited the permissive policy, they could be exploited to make requests to internal services and metadata endpoints on a private network.

The fix involved several changes. First, resolveBrowserSsrFPolicy was updated to generate a strict policy by default (dangerouslyAllowPrivateNetwork: false). Second, functions like fetchCdpChecked were modified to ensure they use a secure policy, while also making a specific exception to allow connections to the loopback address (127.0.0.1) for essential CDP communication. This ensures that the browser can still be controlled locally without re-introducing the SSRF vulnerability.

Vulnerable functions

resolveBrowserSsrFPolicy

extensions/browser/src/browser/config.ts

This function is responsible for creating the SSRF policy for browser interactions. The original implementation created a permissive policy by default, which allowed browser navigations to private networks. This was the root cause of the insecure default configuration.

fetchCdpChecked

extensions/browser/src/browser/cdp.helpers.ts

This function, used for making requests to the Chrome DevTools Protocol (CDP) endpoint, had a fallback to a highly permissive SSRF policy (`allowPrivateNetwork: true`) when no specific policy was provided. This would allow an attacker to make requests to internal services on the private network.

assertCdpEndpointAllowed

extensions/browser/src/browser/cdp.helpers.ts

This function is intended to enforce the SSRF policy for CDP endpoints. It was vulnerable because it relied on the SSRF policy object, which, as established, was permissive by default. Therefore, it would incorrectly allow requests to private network CDP endpoints.

isChromeReachable

extensions/browser/src/browser/chrome.ts

This function checks if a Chrome instance is reachable by making a network request. This operation was subject to the flawed, permissive default SSRF policy, which could allow it to successfully check for services on the private network, leading to information disclosure.

getChromeWebSocketUrl

extensions/browser/src/browser/chrome.ts

This function retrieves the Chrome DevTools WebSocket URL, which involves a network request to a CDP endpoint. This request was vulnerable to SSRF because it was made using the default permissive policy, allowing it to target endpoints on the private network.

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.