CVE-2026-45323

Session compromise via unescaped mesh node name

Published May 28, 2026 · Updated May 28, 2026

Stored XSS in MeshCore Card before 0.3.3 allows physically proximate attackers to execute JavaScript through a crafted node name. The contact card inserts the unescaped adv_name attribute from Home Assistant state into HTML, so a received MeshCore node name becomes executable markup. Any node within direct or repeated LoRa radio range can trigger execution when a user views the card, exposing the user's Home Assistant session and device controls.

CVSS severityUnavailable
Unscored
EPSS probability0.32%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Stored XSS in MeshCore Card before 0.3.3 allows physically proximate attackers to execute JavaScript through a crafted node name. The contact card inserts the unescaped adv_name attribute from Home Assistant state into HTML, so a received MeshCore node name becomes executable markup. Any node within direct or repeated LoRa radio range can trigger execution when a user views the card, exposing the user's Home Assistant session and device controls.

The record

CVE
CVE-2026-45323
Published
May 28, 2026
Updated
May 28, 2026
Vendor
John Pettitt
Product
MeshCore Card
Classifications
T1203
Attack vector
adjacent
Privileges
unauthenticated

Timeline

How it unfolded

  1. May 28, 2026CVE publishedPublication date reported by the CVE source.
  2. May 28, 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.

  1. Affected versionversion=< 0.3.3

What conditions does exploitation require?

Attack vectoradjacent
Required privilegesunauthenticated

What is affected?

John Pettitt · MeshCore Cardversion=< 0.3.3

Published CVSS scores

No CVSS assessment is available in this record.

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectoradjacent
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1203Exploitation for Client Execution

Public exploit references

No public exploit references are available in this record.

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