Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-63641

Vulnerability in magicmirror (CVE-2026-63641)

Summary

Vulnerability in magicmirror (CVE-2026-63641). Risk of unauthorized operations or information disclosure. Exploitable via ipWhitelist. Mitigation: upgrade to 2.37.0 or later.

Original description

The description as published by the source.

Summary

MagicMirror applies ipWhitelist only as Express middleware, but the Socket.IO server is attached directly to the HTTP server without equivalent IP allowlist, origin, or namespace authentication checks. In a documented common deployment where MagicMirror listens on a non-loopback interface but expects ipWhitelist to restrict access, an untrusted network client can connect directly to module Socket.IO namespaces and send arbitrary module-helper notifications. This allows unauthenticated server-side requests through default modules and can reach command execution in the default updatenotification helper when a third-party module update is pending and the attacker supplies the update command through the trusted socket configuration path.

Details

The affected product is the npm package/application magicmirror at version 2.36.0, tested at commit fb41d24ef522e91e802e2a623ff6afbddeb3c9d8 from https://github.com/MagicMirrorOrg/MagicMirror.git.

Default committed settings bind to loopback and allow loopback only (js/defaults.js:8-13), so the remote network impact requires a documented common configuration where the server is reachable beyond loopback. The shipped sample explicitly documents non-loopback binding and IP allowlist behavior: config/config.js.sample:11-20 says address may be another interface or 0.0.0.0/::, and ipWhitelist controls allowed clients.

The trust-boundary issue is that Socket.IO is configured before and outside the Exp…

Source: GitHub Security Advisories (Global) 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-63641 has been found in magicmirror.
Attackers can target a specific entry point like ipWhitelist over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade magicmirror to 2.37.0 or later.
If unsure, ask your IT team or search "magicmirror CVE-2026-63641" on the vendor's site.

CVE-2026-63641 (magicmirror) — CWE-284
Attack surface: ipWhitelist / updatenotification / magicmirror / fb41d24ef522e91e802e2a623ff6afbddeb3c9d8
Patched: 2.37.0 — 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.

❓ What is the problem

A vulnerability (CWE-284) exists in magicmirror. Attackers reach the vulnerable code path via ipWhitelist.

📍 Affected scope

Check the vendor advisory for the affected versions of magicmirror. Attack surface: ipWhitelist / updatenotification / magicmirror / fb41d24ef522e91e802e2a623ff6afbddeb3c9d8.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.37.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'magicmirror' . 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

  1. 1
    Identify exposure identify 
    grep -r 'magicmirror' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で magicmirror を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade magicmirror to 2.37.0

    ステージング環境で 2.37.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm magicmirror
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.37.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details