Vulnerability in magicmirror (CVE-2026-63643)
Summary
Vulnerability in magicmirror (CVE-2026-63643). Risk of unauthorized operations or information disclosure. Exploitable via ADD_CALENDAR. Mitigation: upgrade to 2.37.0 or later.
Original description
The description as published by the source.
Vulnerability — SSRF via ADD_CALENDAR (MagicMirror² calendar)
Analysis of the PoC
exploit-ssrf-calendar.js.
Target:calendar/node_helper.jsof MagicMirror², socket.io namespace/calendar.
Identification
| Field | Value |
|---|---|
| PoC file | exploit-ssrf-calendar.js |
| Endpoint | socket.io namespace /calendar, notification ADD_CALENDAR |
| Precondition | reach the mirror's HTTP port (no authentication required) |
Description
The ADD_CALENDAR handler in calendar/node_helper.js performs a server-side HTTP request to a URL that is fully attacker-controlled, with no SSRF protection whatsoever — unlike the project's hardened /cors endpoint.
Worse, the attacker also controls:
- the authentication headers the server attaches to the request (
auth: { method: "bearer", pass: "..." }); - the
selfSignedCertflag, which disables TLS verification of the server-side request.
When the target's response is valid iCal, the server parses the events and sends them back to the attacker via CALENDAR_EVENTS — turning the SSRF into full data exfiltration (response body read). Against non-iCal responses it remains a blind SSRF (the attacker still forces the server-side request, they just don't see the body).
Root cause: unauthenticated socket.io channel + permissive CORS
The socket.io server accepts connections from any origin and with no authentication:
const io = new Server…
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-63643 has been found in magicmirror.
Attackers can target a specific entry point like ADD_CALENDAR 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-63643" on the vendor's site.
CVE-2026-63643 (magicmirror) — CWE-441
Attack surface: ADD_CALENDAR / selfSignedCert / CALENDAR_EVENTS
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.
A vulnerability (CWE-441) exists in magicmirror. Attackers reach the vulnerable code path via ADD_CALENDAR.
Check the vendor advisory for the affected versions of magicmirror. Attack surface: ADD_CALENDAR / selfSignedCert / CALENDAR_EVENTS.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.37.0.
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 '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 patch patch
Upgrade magicmirror to 2.37.0ステージング環境で 2.37.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-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