p PatchFirst

CVE-2026-63641

CVE-2026-63641 · MagicMirror Socket.IO module namespaces bypass configured IP whitelist and allow unauthenticated server-side actions

This page contains facts from public vulnerability sources. Check the original advisory before updating.

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.

CVSS 2.3 · Low · EPSS 0.4% · Fix available

Published
Updated

Stack: node

Affected products and versions

  • magicmirror

    Versions
    • < 2.37.0: Affected

    No fix published

  • magicmirror npm

    Affected ranges
    • SEMVER: < 2.37.0

    Update to 2.37.0

Original sources

Check your server →