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.
Original description
The description as published by the source.
Summary
When hideConfigSecrets: true is enabled, MagicMirror redacts SECRET_* environment placeholders in the HTTP /config response, but the shared node-helper socket dispatcher expands **SECRET_NAME** placeholders in every inbound socket payload before passing it to module helpers. Any client that can connect to a loaded module namespace can send a placeholder such as **SECRET_API_KEY** and cause the server to substitute the real environment variable into the helper payload. Helpers that echo attacker-controlled payload fields, such as the default weather helper error path, can return the secret value to the socket client.
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.
The secret-redaction feature is implemented during config loading:
js/utils.js:117-123loads aconfig.envfile next to the config file intoprocess.envwhen present.js/utils.js:130-151creates both a full config and a redacted config.js/utils.js:137-140redacts environment variables whose names start withSECRET_to**SECRET_NAME**in the redacted config whenhideConfigSecrets: trueis present.js/server.js:112-125returns eitherconfigObj.redactedConforconfigObj.fullConffrom/configdepending onconfig.hideConfigSecrets.
The disclosure root cause is the inbound socket dispatcher:
- `js…
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-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.
Information disclosure (CWE-200) exists in magicmirror. Attackers reach the vulnerable code path via magicmirror without authentication.
Check the vendor advisory for the affected versions of magicmirror. Attack surface: magicmirror / fb41d24ef522e91e802e2a623ff6afbddeb3c9d8 / config.env / process.env.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 2.37.0.
Workaround: set hideConfigSecrets: true
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
-
1Identify exposure identify
grep -r 'magicmirror' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
magicmirrorを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
set hideConfigSecrets: trueパッチが適用されるまでの応急処置として、set hideConfigSecrets: true を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade magicmirror to 2.37.0ステージング環境で 2.37.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com