Is CVE-2026-63643 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-63643 being exploited in the wild.

How severe is CVE-2026-63643?

Medium severity, with a CVSS score of 4, published 18 August 2026.

Which products and versions are affected?

magicmirror (npm) SEMVER:introduced=0,fixed=2.37.0.

Is there a fix for CVE-2026-63643?

Yes. magicmirror (npm): upgrade to 2.37.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-63643 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-63643?

Check whether you run magicmirror (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-63643: MagicMirror server-side request forgery in calendar module

CVE-2026-63643 · Severity: medium · CVSS 4 · Published 2026-08-18

MagicMirror is a smart display platform used to show calendars and other information on mirror screens. An unauthenticated attacker with network access to the mirror's HTTP port can force the server to make arbitrary HTTP requests to internal or external targets, including cloud metadata services and private network hosts. When calendar responses are returned in iCalendar format, the attacker can read the full response body, enabling data theft from services not directly accessible to the attacker.

Technologies: magicmirror (npm). Vendors: npm.

Quick answers

Is CVE-2026-63643 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-63643 being exploited in the wild.
How severe is CVE-2026-63643?: Medium severity, with a CVSS score of 4, published 18 August 2026.
Which products and versions are affected?: magicmirror (npm) SEMVER:introduced=0,fixed=2.37.0.
Is there a fix for CVE-2026-63643?: Yes. magicmirror (npm): upgrade to 2.37.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-63643 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-63643?: Check whether you run magicmirror (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

magicmirror (npm): upgrade to 2.37.0 or later
```
npm install magicmirror@2.37.0
```

Technical details

The calendar module in MagicMirror accepts a socket.io notification called `ADD_CALENDAR` without authentication, allowing any browser or process reaching the mirror's port to trigger it. The handler passes an attacker-controlled URL, authentication headers, and a `selfSignedCert` flag directly to a calendar fetcher that makes a server-side HTTP request. The socket.io server is configured with permissive CORS (`origin: /.*$/`) and no connection-level authentication (CWE-306, CWE-918). If the server's response is valid iCalendar format, events are parsed and sent back to the attacker via `CALENDAR_EVENTS`, enabling full response body exfiltration. The attacker can also inject arbitrary `Authorization: Bearer` headers (confused deputy attack) and disable TLS certificate verification. The vulnerability affects versions before 2.37.0 and is reachable over the network if the mirror's HTTP port is accessible.

Affected products

MagicMirror Organization MagicMirror < 2.37.0

Identifiers

CVE-2026-63643
GHSA-w6x9-28jw-hq7j

Timeline

2026-08-18: disclosed: GitHub advisory published
2026-07-01: patched: Fix released in version 2.37.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.