Unauthenticated server-side actions via Socket.IO whitelist bypass
Published Aug 18, 2026 · Updated Aug 18, 2026
Improper access control in Socket.IO handling in MagicMirror² before 2.37.0 allows adjacent-network attackers to trigger server-side actions. In js/server.js, Socket.IO is attached directly to the HTTP server without the ipWhitelist enforcement later applied as Express middleware, and js/node_helper.js forwards arbitrary namespace events and payloads to socketNotificationReceived. Exposure requires a non-loopback deployment that relies on ipWhitelist for network restriction; default helpers can then be driven into server-side requests, module-state changes, and conditional child_process.exec when a pending third-party module update exists.
Summary
What happened
Improper access control in Socket.IO handling in MagicMirror² before 2.37.0 allows adjacent-network attackers to trigger server-side actions. In js/server.js, Socket.IO is attached directly to the HTTP server without the ipWhitelist enforcement later applied as Express middleware, and js/node_helper.js forwards arbitrary namespace events and payloads to socketNotificationReceived. Exposure requires a non-loopback deployment that relies on ipWhitelist for network restriction; default helpers can then be driven into server-side requests, module-state changes, and conditional child_process.exec when a pending third-party module update exists.
The record
- CVE
- CVE-2026-63641
- Published
- Aug 18, 2026
- Updated
- Aug 18, 2026
- Vendor
- MagicMirror
- Product
- MagicMirror²
- Classifications
- CWE-284
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 18, 2026CVE publishedPublication date reported by the CVE source.
- Aug 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.37.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub advisory safe local PoCsproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo