# CVE-2026-45323: MeshCore Card: XSS vulnerability through meshcore node name

> An attacker within radio range can execute arbitrary JavaScript in the Home Assistant frontend via unescaped node names in the MeshCore Card plugin.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 May 2026
- **Updated:** 29 May 2026
- **Also known as:** GHSA-5vrg-xpcj-xppc

## What is CVE-2026-45323?

CVE-2026-45323 is a critical cross-site scripting vulnerability in jpettitt meshcore-card, published on 28 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

MeshCore Card provides MeshCore Lovelace card for Home Assistant. Prior to 0.3.3, Meshcore node names are rendered without HTML escaping in meshcore-card, allowing any node within direct or indirect (repeated) radio range to execute arbitrary javascript in the Home Assistant frontend of anyone viewing the card. This vulnerability is fixed in 0.3.3.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Jpettitt Meshcore Card.

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

No fix has been published for CVE-2026-45323 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-45323 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45323 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45323 is a critical cross-site scripting vulnerability in jpettitt meshcore-card, published on 28 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45323 exists.

Affected product: jpettitt meshcore-card. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-45323/ (Markdown: https://insights.sbomify.com/CVE-2026-45323/index.md)
```

## Sources

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

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