Skip to main content
VulnerabilityPublished

CVE-2026-63641: MagicMirrorOrg MagicMirror · Improper Access Control

Affects MagicMirrorOrg MagicMirrorSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 2.3 Low : upgrade to 2.37.0 when convenient.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 4.0 base score
2.3Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.37.0
CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade MagicMirror and magicmirrororg/MagicMirror to 2.37.0.

Affected software

ProductAffectedFixed in
MagicMirrorOrgMagicMirrorAffected
  • <2.37.0
Fixed in
  • 2.37.0
GitHubmagicmirrororg/MagicMirrorpkg:github/magicmirrororg/MagicMirrorOther threatsAffected
  • <2.37.0
Fixed in
  • 2.37.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade MagicMirror to version 2.37.0 or later, where this improper access control vulnerability is fixed. No other official remediation or temporary fixes are documented. Until upgrading, restrict network access to trusted clients only to reduce exposure.

Description

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.

References

Community reviews

Loading reviews…