MagicMirror socket payload secret placeholder expansion can disclose SECRET_* environment variables

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.3 · CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2026-63640: 0.30% estimated exploitation activity in the next 30 days; percentile 22.51 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary When hideConfigSecrets: true is enabled, MagicMirror redacts SECRET environment placeholders in the HTTP /config response, but the shared node-helper socket dispatcher expands SECRETNAME placeholders in every inbound socket payload before passing it to module helpers. Any client that can connect to a loaded module namespace can send a placeholder such as SECRETAPIKEY and cause the server to substitute the real environment variable into the helper payload. Helpers that echo attacker-controlled payload fields, such as the default weather helper error path, can return the secret value to the socket client. Details The affected product is the npm package/application magicmirror at version 2.36.0, tested at commit fb41d24ef522e91e802e2a623ff6afbddeb3c9d8 from https://github.com/MagicMirrorOrg/MagicMirror.git. The secret-redaction feature is implemented during config loading: - js/utils.js:117-123 loads a config.env file next to the config file into process.env when present. -…

Published by the source

18 Aug 2026, 18:00 UTC

Last modified by the source

18 Aug 2026, 18:00 UTC

Source last checked

26 Oct 2026, 13:01 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-q4gh-4ffp-5cg8

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-63640

Advisory: MagicMirror socket payload secret placeholder expansion can disclose SECRET_* environment variables
IDs: CVE-2026-63640, GHSA-q4gh-4ffp-5cg8
Record: https://patchnext.com/advisories/cve-2026-63640 (revision 1, source checked 26 Oct 2026, 13:01 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: magicmirror 2.37.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm magicmirror: affected < 2.37.0; fixed in 2.37.0

## Suggested inspection (read-only)
- `npm ls magicmirror --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on magicmirror.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-q4gh-4ffp-5cg8 (GitHub-reviewed advisory GHSA-q4gh-4ffp-5cg8 lists affected ranges: npm magicmirror >=0 <2.37.0)

Commands are suggestions: review each one before running it.