Loading vulnerability…
CVE-2026-59723 is a high-severity cross-origin WebSocket hijacking vulnerability in Cline prior to version 3.0.30. The issue affects the Cline Hub dashboard server launched by the cline dashboard command. The /browser WebSocket endpoint accepts connections without validating the Origin header, and when ROOM_SECRET is unset for local 127.0.0.1 binds, isAuthorizedBrowserRequest() can permit attacker-controlled browser requests. Under these conditions, a malicious website visited by a user can establish a WebSocket connection to the local dashboard service and send desktopCommand frames. This can be used to read workspace state, modify MCP settings, modify provider settings, and trigger command execution when a provider or model is configured. The vulnerability is fixed in Cline version 3.0.30.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
ROOM_SECRET is configured, especially in any non-local or less-trusted deployment scenario. Restrict access to the dashboard service to trusted local contexts only, minimize or disable provider/model configurations where feasible, and avoid visiting untrusted websites while the vulnerable dashboard is running. Additional defensive hardening includes enforcing strict Origin validation for WebSocket connections and limiting browser access to the local service.Patch, then assume compromise.
/browser WebSocket handling. If operationally relevant, review the referenced fix associated with commit d09270940f5746f288cfc4a5039b46a2f4d5d01e and release cli-v3.0.30. After upgrading, verify that the dashboard server properly enforces WebSocket origin validation and that dashboard access controls are functioning as intended.No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.