CVE-2026-43576
Analyzed Analyzed - Analysis Complete
OpenClaw SSRF via Unvalidated WebSocket Debugger URL

Publication date: 2026-05-06

Last updated on: 2026-05-07

Assigner: VulnCheck

Description
OpenClaw before 2026.4.5 contains a server-side request forgery vulnerability in the CDP /json/version WebSocket endpoint that allows attackers to pivot to untrusted second-hop targets. The webSocketDebuggerUrl response field is not properly validated, enabling attackers to redirect connections to arbitrary hosts and perform SSRF-style attacks.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-06
Last Modified
2026-05-07
Generated
2026-05-18
AI Q&A
2026-05-07
EPSS Evaluated
2026-05-11
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
openclaw openclaw to 2026.4.5 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
CWE-601 The web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect.
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The provided information does not specify how the CVE-2026-43576 vulnerability impacts compliance with common standards and regulations such as GDPR or HIPAA.


Can you explain this vulnerability to me?

This vulnerability exists in OpenClaw versions before 2026.4.5 and involves a server-side request forgery (SSRF) issue in the CDP /json/version WebSocket endpoint.

Specifically, the webSocketDebuggerUrl response field is not properly validated, which allows attackers to redirect connections to arbitrary hosts.

This enables attackers to pivot to untrusted second-hop targets and perform SSRF-style attacks.


How can this vulnerability impact me? :

The vulnerability can allow an attacker to redirect server requests to arbitrary hosts, potentially accessing internal or protected resources that are not normally accessible.

This can lead to unauthorized access or information disclosure by leveraging the server as a proxy to reach untrusted or internal systems.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability involves manipulation of the CDP /json/version WebSocket URL, specifically the webSocketDebuggerUrl response field being redirected to untrusted hosts. Detection can focus on monitoring WebSocket connections to the /json/version endpoint and inspecting the webSocketDebuggerUrl values for unexpected or unauthorized hosts.

Commands or methods to detect this vulnerability might include:

  • Using network traffic analysis tools (e.g., tcpdump, Wireshark) to capture WebSocket handshake requests and responses to the /json/version endpoint and checking for suspicious webSocketDebuggerUrl values.
  • Using curl or similar HTTP clients to query the /json/version endpoint and manually inspecting the webSocketDebuggerUrl field for redirection to unexpected hosts, for example:
  • curl -s http://<target-host>:<port>/json/version | grep webSocketDebuggerUrl
  • Reviewing application logs or WebSocket connection logs for attempts to connect to or redirect through unexpected hosts.

Note that no explicit detection commands are provided in the resources, so these suggestions are based on the nature of the vulnerability involving WebSocket URL redirection.


What immediate steps should I take to mitigate this vulnerability?

The primary and immediate mitigation step is to upgrade OpenClaw to version 2026.4.5 or later, as this version includes the patch that properly validates the webSocketDebuggerUrl and prevents SSRF attacks.

Additional mitigation steps include:

  • Restrict network access to the CDP /json/version WebSocket endpoint to trusted users or systems only.
  • Implement network-level controls or firewall rules to block unauthorized outbound connections that could be used in SSRF pivoting.
  • Monitor and audit WebSocket connections and logs for suspicious activity related to unexpected host redirections.

The fix involves hardening validation of WebSocket endpoints to ensure connections are only allowed to authorized hosts, as implemented in the patched versions.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart