Vulnerability in line-desktop-mcp (CVE-2026-49357)
Summary
Vulnerability in line-desktop-mcp (CVE-2026-49357). Risk of unauthorized operations or information disclosure. Exploitable via fbed0d2d3048e63f48a356a1267ed8ec5e78f3ae. Mitigation: upgrade to 1.1.2 or later.
Original description
The description as published by the source.
Line Desktop MCP is a project that, while unaffiliated with the official line-bot-mcp-server, allows users to directly operate the LINE Desktop application on Windows or Mac via MCP. line-desktop-mcp supports a --http-mode Streamable HTTP transport for use with clients such as n8n. In this mode the server binds to 0.0.0.0 and exposes the MCP /mcp endpoint without an MCP-layer authentication check. Prior to version 1.1.2, any network client that can reach the port can initialize a session, list tools, and call tools that read LINE Desktop chat history or send LINE messages through the already logged-in desktop application. Version 1.1.2 fixes the issue.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-49357 has been found in line-desktop-mcp.
Attackers can target a specific entry point like fbed0d2d3048e63f48a356a1267ed8ec5e78f3ae over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade line-desktop-mcp to 1.1.2 or later.
If unsure, ask your IT team or search "line-desktop-mcp CVE-2026-49357" on the vendor's site.
CVE-2026-49357 (line-desktop-mcp) — CWE-306
Attack surface: fbed0d2d3048e63f48a356a1267ed8ec5e78f3ae / main / README.md / get_line_chatroom_history_default
Patched: 1.1.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-306) exists in line-desktop-mcp. Attackers reach the vulnerable code path via fbed0d2d3048e63f48a356a1267ed8ec5e78f3ae.
Check the vendor advisory for the affected versions of line-desktop-mcp. Attack surface: fbed0d2d3048e63f48a356a1267ed8ec5e78f3ae / main / README.md / get_line_chatroom_history_default.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.1.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'line-desktop-mcp' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'line-desktop-mcp' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
line-desktop-mcpを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade line-desktop-mcp to 1.1.2ステージング環境で 1.1.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com