Medium Cross-site scripting exploit reference

CVE-2026-33044 — Home Assistant has stored XSS in Map-card through malicious device name

Home Assistant is open source home automation software that puts local control and privacy first. Starting in version 2020.02 and prior to version 2026.01, an authenticated party can add a malicious name to their device entity, allowing for Cross-Site Scripting attacks against anyone who can see a dashboard with a Map-card which includes that entity. It requires that the victim hovers over an information point. Version 2026.01 fixes the issue.

Published Mar 27, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: GitHub_M

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.3% (30-day exploitation probability)+3
Technical severity (medium)+3
CISA SSVC: exploitation "poc"+5

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.28%

ahead of 19% of scored CVEs · Oct 15, 2026

Affects

Home-assistant

Core and 1 more

CVSS base

5.4

Medium · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

Proof of concept

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Home-assistant Core, Home-assistant Home-assistant).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Exploitation requires user interaction: tighten email/web filtering and warn affected users.
Search available logs for exploit probes matching the vulnerability class (cross-site scripting), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Home-assistant	Core	version >= 2020.02, < 2026.01	Vulnerable	CVE Program (cve.org) e CISA ADP
Home-assistant	Home-assistant	≥ 2020.02 and < 2026.1.0	Vulnerable	NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

Low

User interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
7.3	CVSS 4.0	High	—	—	security-advisories@github.com via NIST National Vulnerability Database
7.3	CVSS 4.0	High	—	—	GitHub_M via CVE Program (cve.org) e CISA ADP
5.4	CVSS 3.1	Medium	2.3	2.7	nvd@nist.gov via NIST National Vulnerability Database

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-79 · Cross-site Scripting (XSS)

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 15, 2026 · 3 reading(s) · max 0.28%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Monitor CSP violation reports and script payloads in reflected parameters.

web/proxy/WAF logsnetwork IDS/IPSapplication logs

Timeline

What happened to this CVE, newest first.

2026
Affected products added · home-assistant/core
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
CVSS changed · 5.4
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
CVE published
Mar 27, 2026 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

1 on the record

github.com/home-assistant/core/security/advisories/GHSA-r584-6283-p7xc
Exploit, Vendor Advisory, x_refsource_CONFIRM, NIST National Vulnerability Database

Elsewhere on this site

Home-assistant
every CVE for this vendor

Cross-site scripting
same class

CWE-79
other pages naming this weakness

Related CVEs (same products)

Critical CVE-2026-91130 Home Assistant: XSS in Statistics Graph Card 23d
Medium CVE-2026-91129 Home Assistant: mDNS Server-Side Request Forgery 23d
Medium CVE-2026-59717 Home Assistant Companion: `homeassistant://invite` Deep Link Credential Phishing Aug 7, 2026
High CVE-2026-66060 Home Assistant: Unconfirmed NFC/QR tag scans allow silent automation execution by untrusted callers Aug 7, 2026
High CVE-2026-66061 Home Assistant: iOS Companion app forwards NFC/QR tag scans without confirmation, enabling silent automation execution Aug 7, 2026
High CVE-2026-64824 Home Assistant Core < 2026.7.0 Symlink Path Traversal RCE via backup-restore Jul 21, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-33044 is "Home Assistant has stored XSS in Map-card through malicious device name", rated Medium. It affects Core (Home-assistant); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.4 describes technical severity. EPSS 0.28% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.