CVE-2026-43527
Published: 05 May 2026
Description
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.
Likely Mitigating ControlsAI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Penetration testing attempts server-side requests to internal resources, identifying SSRF weaknesses for remediation.
Requires documented secure initialization practices and avoidance of insecure defaults in configuration baselines.
Reviewing and updating baseline when components are installed or upgraded prevents initialization with insecure defaults.
Requiring explicit configuration to minimal functionality overrides insecure defaults that would otherwise enable excess capabilities.
Tailoring replaces or augments insecure default initializations with system-specific values and compensating controls before deployment.
Central configuration overrides or replaces insecure default initializations that would otherwise be left unchanged on each system.
SCRM practices during acquisition and configuration management address insecure default initializations shipped by vendors.
Scans detect resources initialized with insecure defaults that create exploitable conditions.
Security SummaryAI
CVE-2026-43527 is a server-side request forgery (SSRF) vulnerability affecting OpenClaw versions before 2026.4.14, published on 2026-05-05. The issue stems from a misconfigured browser SSRF policy that permits private-network navigation by default, allowing browser-driven requests to reach unintended destinations. It is associated with CWE-918 (Server-Side Request Forgery) and CWE-1188 (Insecure Default Initialization of Resource Consumption), and carries a CVSS v3.1 base score of 7.7 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N).
Low-privileged remote attackers (PR:L) can exploit this vulnerability over the network with low attack complexity and no user interaction required. By leveraging the permissive policy, they can craft requests that cause the OpenClaw server to access internal services or metadata endpoints, potentially exposing sensitive information with high confidentiality impact due to the changed scope (S:C).
Mitigation patches are provided in OpenClaw GitHub commits 024f4614a1a1831406e763adc40ef226e3d5e9ed, 1dabfef28db523e7de81edeb3dd689e9171236a2, 213c36cf51121ef6c05cfccd78037371f968f31a, and 7eecfa411df3d12e6b810e6ca5df47254fc3db3f. Additional details are available in the GitHub security advisory at GHSA-53vx-pmqw-863c. Affected users should upgrade to OpenClaw 2026.4.14 or later to address the vulnerability.
Details
- CWE(s)
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
SSRF in public-facing server directly enables T1190 exploitation; explicit metadata endpoint access maps to T1522 discovery and T1552.005 credential retrieval from cloud instance metadata.