CVE-2026-17458 Overview
CVE-2026-17458 is a Server-Side Request Forgery (SSRF) vulnerability affecting mf-yang openclaw-cn versions up to 0.2.1. The flaw resides in the clickViaPlaywright function within src/browser/routes/agent.act.ts, part of the Browser Control HTTP API component. Attackers can manipulate request parameters remotely to force the server to issue arbitrary HTTP requests on their behalf. The exploit has been made public, and the project maintainers have not responded to the issue report at time of disclosure. The weakness is classified under CWE-918.
Critical Impact
Remote authenticated attackers can coerce the server into issuing arbitrary requests, potentially reaching internal services, cloud metadata endpoints, or non-public network resources.
Affected Products
- mf-yang openclaw-cn versions up to and including 0.2.1
- Component: Browser Control HTTP API
- Affected function: clickViaPlaywright in src/browser/routes/agent.act.ts
Discovery Timeline
- 2026-07-26 - CVE-2026-17458 published to NVD
- 2026-07-27 - Last updated in NVD database
Technical Details for CVE-2026-17458
Vulnerability Analysis
The vulnerability exists in the clickViaPlaywright function of the Browser Control HTTP API. The function drives browser automation through Playwright and accepts input that influences the target URL used during the click action. Because the input is not sufficiently validated or restricted to an allowlist, an attacker can supply a crafted URL that the server-side browser instance will request. This is a canonical CWE-918 Server-Side Request Forgery pattern. Exploitation can be initiated remotely over the network and requires only low privileges. Public availability of the exploit increases opportunistic risk for exposed deployments.
Root Cause
The root cause is missing validation of user-supplied URL or navigation parameters passed into clickViaPlaywright. The route accepts destinations without enforcing scheme restrictions, host allowlists, or blocks on private and link-local address ranges. As a result, a controlled browser session will follow requests to arbitrary internal or external endpoints selected by the caller.
Attack Vector
An attacker submits a request to the Browser Control HTTP API endpoint that invokes clickViaPlaywright with an attacker-chosen URL. The server-side Playwright browser then issues a request to that destination from within the trust boundary of the host. Targets typically include cloud instance metadata services, internal administrative interfaces, and services bound to loopback or private ranges. See the GitHub Issue #562 Discussion and the VulDB CVE-2026-17458 Entry for reference details. No verified proof-of-concept code is included here; refer to the linked advisories for technical specifics.
Detection Methods for CVE-2026-17458
Indicators of Compromise
- Outbound HTTP requests from the openclaw-cn service process to private address ranges such as 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, or loopback 127.0.0.0/8.
- Requests from the browser automation host to cloud metadata endpoints such as 169.254.169.254.
- Unexpected invocations of the /agent/act route or related Browser Control HTTP API endpoints with externally supplied URLs.
Detection Strategies
- Inspect application and reverse-proxy logs for calls to the clickViaPlaywright handler with URL parameters targeting internal hosts, non-HTTP schemes, or metadata IPs.
- Correlate outbound network flows from the Playwright browser process against an allowlist of expected destinations.
- Alert on any DNS resolution from the openclaw-cn host for internal service names not previously observed.
Monitoring Recommendations
- Enable verbose access logging on the Browser Control HTTP API and forward logs to a centralized analytics platform.
- Track process-level egress from the Node.js runtime hosting openclaw-cn using host-based network telemetry.
- Baseline normal browser automation destinations and alert on deviations, especially requests to RFC1918 space or cloud metadata services.
How to Mitigate CVE-2026-17458
Immediate Actions Required
- Restrict network exposure of the Browser Control HTTP API so it is not reachable from untrusted networks.
- Place the openclaw-cn service behind authentication and IP allowlisting until a fix is released.
- Block outbound access from the openclaw-cn host to internal management ranges and cloud metadata endpoints at the network layer.
Patch Information
No vendor patch is available at time of publication. The maintainer of mf-yang/openclaw-cn has not responded to the issue report referenced in the advisory. Track the GitHub Repository for OpenClaw and GitHub Issue #562 Discussion for updates. Users running versions up to 0.2.1 should assume exposure until a patched release is published.
Workarounds
- Deploy the service inside a network segment that has no route to internal management interfaces, cloud metadata endpoints, or sensitive backends.
- Add an egress proxy that enforces a strict destination allowlist for outbound requests originating from the Playwright browser process.
- Introduce a reverse-proxy rule that rejects requests to clickViaPlaywright when the URL parameter targets private, loopback, or link-local addresses.
- Disable the Browser Control HTTP API entirely if it is not required in the deployment.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
