UTC
High

Streamable HTTP mode exposes LINE Desktop read/send tools without MCP authentication

CVE-2026-49357 · GHSA-4hf8-5mjm-rfgq · published 2026-06-26

Severity
High
CVSS score
8.8
Chance of exploitation (EPSS)
0.56%
Fixed in
1.1.2
  • Exploitation No known exploitation
  • Automatable Yes
  • Technical impact Partial
  • CISA SSVC
What it is

An unauthenticated network client can read LINE chat history through the MCP history tools and can send LINE messages through the send-message tools, including sendmessageauto when the tool call requests immediate sending. The attacker does not need LINE credentials or a LINE API token; they only need network reachability to the MCP HTTP port. The practical impact is disclosure of private LINE conversations and unauthorized messages sent as the logged-in desktop user.

What to do

Upgrade line-desktop-mcp to 1.1.2 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

Require authentication before accepting Streamable HTTP MCP sessions or tool calls. For example: require a bearer token or local secret when --http-mode is used; bind HTTP mode to 127.0.0.1 by default unless the operator explicitly opts into network exposure; refuse to start 0.0.0.0 HTTP mode without authentication; document that host.docker.internal / n8n setups must still authenticate to the MCP server. A defense-in-depth improvement would also keep sendmessageauto disabled unless explicitly enabled by a server-side flag, because it converts MCP tool access into immediate message sending as the desktop user.

Affected
PackageRegistryAffectedFixed in
line-desktop-mcpnpm<= 1.1.11.1.2

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].