Live › vulnerability › CVE-2026-62863
MoLing is an MCP server that controls a computer and browser. In SSE mode its endpoints do not check who is calling and send a permissive CORS header, so a malicious web page the user visits can read a session ID and send tool calls that read or write local files or run commands.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-30 21:25 UTC. All times on this page are UTC.
Teams that run MoLing 0.4.x or earlier in SSE mode (started with -l) on a machine where a browser is used. Exposure depends on which tools are configured, since file and command tools make the impact worse. Installations on 0.5.0 or later, or not running SSE mode, are not affected per the sources.
No product ranges from the sources yet.
0.5.0.-l (serving /sse and /message).0.5.0Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
MoLing is a computer-use and browser-use based MCP server. Prior to 0.5.0, when MoLing runs in SSE mode using -l, its /sse and /message HTTP endpoints do not authenticate requests and the mcp-go dependency sets Access-Control-Allow-Origin: *. A malicious web page can open a cross-origin EventSource to /sse, including a loopback listener, and read the endpoint event to obtain sessionId. After a victim running SSE mode visits that page, the attacker can use the disclosed sessionId against /message to send unauthorized MCP tool calls. Depending on the configured tools, those calls can read or write local files, execute commands or perform other actions. Binding only to loopback does not prevent this browser-mediated attack. This issue is fixed in version 0.5.0.
This page as .md · .json · in your agent: get_signal("CVE-2026-62863")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.