CVE-2026-63643: MagicMirror: ssrf calendar .js
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).
References
- github.com/MagicMirrorOrg/MagicMirror/commit/58c2a5e675a7d367b64d72e1d35680d202ff5c9f
- github.com/MagicMirrorOrg/MagicMirror/pull/4169
- github.com/MagicMirrorOrg/MagicMirror/releases/tag/v2.37.0
- github.com/MagicMirrorOrg/MagicMirror/security/advisories/GHSA-w6x9-28jw-hq7j
- github.com/advisories/GHSA-w6x9-28jw-hq7j
- nvd.nist.gov/vuln/detail/CVE-2026-63643
Code Behaviors & Features
Detect and mitigate CVE-2026-63643 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →