← Back
CVE-2026-63640
medium
CVSS 4.3
Information Disclosure in magicmirror (CVE-2026-63640)
Summary
vulnerability in magicmirror (CVE-2026-63640). Risk of unauthorized operations or information disclosure. Exploitable via ``magicmirror``. Mitigation: upgrade to `2.37.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-63640** has been found in magicmirror.
Attackers can target a specific entry point like ``magicmirror`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade magicmirror to **2.37.0** or later.
If unsure, ask your IT team or search "magicmirror CVE-2026-63640" on the vendor's site.
CVE-2026-63640 (magicmirror) — CWE-200 / CVSS v3 4.3
Attack vector: adjacent-network / unauthenticated / no user interaction
Attack surface: `magicmirror` / `fb41d24ef522e91e802e2a623ff6afbddeb3c9d8` / `config.env` / `process.env`
Patched: `2.37.0` — apply immediately
Workaround: set hideConfigSecrets: true
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
**information disclosure** (CWE-200) exists in magicmirror. Attackers reach the vulnerable code path via ``magicmirror`` without authentication.
📍 Affected scope
magicmirror — . Attack surface: `magicmirror` / `fb41d24ef522e91e802e2a623ff6afbddeb3c9d8` / `config.env` / `process.env`.
🔥 Severity
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.37.0**.
🛡️ Workaround
Workaround: set hideConfigSecrets: true
🔍 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 (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'magicmirror' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `magicmirror` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
set hideConfigSecrets: trueパッチが適用されるまでの応急処置として、set hideConfigSecrets: true を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade magicmirror to 2.37.0ステージング環境で 2.37.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
magicmirror
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.37.0"}]}]