CVE-2026-63641

What it is

MagicMirror² is an open source modular smart mirror platform. Prior to 2.37.0, MagicMirror applies ipWhitelist only as Express middleware, while the Socket.IO server in js/server.js is attached directly to the HTTP server without equivalent IP allowlist, origin, or namespace authentication checks. In a documented non-loopback deployment that relies on ipWhitelist, an unauthenticated adjacent-network client can connect directly to module Socket.IO namespaces, and js/node_helper.js dispatches arbitrary events and payloads to socketNotificationReceived. The default newsfeed and calendar helpers can make server-side requests to attacker-selected URLs, while the default updatenotification helper can reach child_process.exec when a third-party module update is pending and the attacker supplies an update command through the socket CONFIG path. This can expose internal services, manipulate module-helper state, and conditionally execute commands. This issue is fixed in version 2.37.0.

At a glance

Exploitability

Can be exploited from the same network segment without logging in. Limited direct impact.

Exploit odds

0.4% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-08-18 18:19 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-22 22:10 UTC Last updatedMost recent change to the record

Details

Published

2026-08-18 18:19 UTC

Last modified

2026-10-22 22:10 UTC

Exploit probability

0.4% · EPSS, next 30 days

Weakness

CWE-284 · Improper access control

Record status

Deferred

Attack profile CVSS 4.0 · 2.3

Attack vector

Adjacent network

Complexity

Low

Attack requirements

Present

Privileges needed

None

User interaction

None

Confidentiality

Low

Integrity

Low

Availability

Low