# CVE-2026-63643: MagicMirror: ssrf calendar .js

> An unauthenticated attacker can trigger server-side requests via the calendar module to exfiltrate internal data or bypass TLS verification.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Aug 2026
- **Updated:** 19 Aug 2026
- **Also known as:** GHSA-w6x9-28jw-hq7j

## What is CVE-2026-63643?

CVE-2026-63643 is a medium-severity server-side request forgery vulnerability in MagicMirrorOrg MagicMirror, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MagicMirror² is an open source modular smart mirror platform. Prior to 2.37.0, the ADD_CALENDAR handler in defaultmodules/calendar/node_helper.js accepts an attacker-controlled URL, authentication data, and selfSignedCert setting through the unauthenticated Socket.IO namespace /calendar. The handler passes these fields to CalendarFetcher, causing a server-side request without SSRF validation and optionally disabling TLS verification. When the response is valid iCal, CALENDAR_EVENTS returns parsed event data to the attacker, allowing internal-service response data to be exfiltrated; other responses still provide a blind request and timing primitive. This issue is fixed in version 2.37.0.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-441 (Unintended Proxy or Intermediary)

## Which versions are affected by CVE-2026-63643?

2 open source packages ship an affected version, including magicmirror.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `magicmirror` | npm | All versions | 2.37.0 |
| `magicmirror` | npm | All versions | 2.37.0 |

## How do I fix CVE-2026-63643?

Upgrade magicmirror to 2.37.0 or later.

## Is CVE-2026-63643 being exploited?

There is no known exploitation of CVE-2026-63643 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-63643 and fix it if it is affected.

What it is: CVE-2026-63643 is a medium-severity server-side request forgery vulnerability in MagicMirrorOrg MagicMirror, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-63643 in the wild and no public exploit code.

Affected packages and fixed versions:
- magicmirror (npm): affected all versions; fixed in 2.37.0
- magicmirror (npm): affected all versions; fixed in 2.37.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-63643/ (Markdown: https://insights.sbomify.com/CVE-2026-63643/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-63643
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-63643
- OSV: https://osv.dev/vulnerability/CVE-2026-63643

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-63643/
Summaries are generated and may contain mistakes; the official description above is the record.