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

> An authenticated attacker can inject malicious scripts via device names, leading to XSS when victims view a Map-card dashboard.

- **Severity:** High 7.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 Mar 2026
- **Updated:** 2 Apr 2026
- **Also known as:** GHSA-r584-6283-p7xc, PYSEC-2026-2517

## What is CVE-2026-33044?

CVE-2026-33044 is a high-severity cross-site scripting vulnerability in home-assistant core, published on 27 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

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.

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

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

3 open source packages ship an affected version, including homeassistant. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `homeassistant` | PyPI | From 2020.02 | 2026.01 |
| `homeassistant` | PyPI | From 2020.02 | 2026.01 |
| `homeassistant` | PyPI | From 2020.02 | 2026.01 |

Products: Home-Assistant Home-Assistant.

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

Upgrade homeassistant to 2026.01 or later.

## Is CVE-2026-33044 being exploited?

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

## Other vulnerabilities in home-assistant core

- [CVE-2023-27482](https://insights.sbomify.com/CVE-2023-27482/): Auth bypass in core (critical 10.0)
- [CVE-2023-41895](https://insights.sbomify.com/CVE-2023-41895/): Cross-site Scripting via auth_callback login in Home Assistant Core (high 8.8)
- [CVE-2023-41897](https://insights.sbomify.com/CVE-2023-41897/): Lack of XFO header allows clickjacking in Home Assistant Core (high 8.8)
- [CVE-2026-54317](https://insights.sbomify.com/CVE-2026-54317/): Home Assistant: Konnected alarm-panel switch state and zone topology disclosed to unauthenticated actors on the LAN (high 7.6)
- [CVE-2020-36517](https://insights.sbomify.com/CVE-2020-36517/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-33044 is a high-severity cross-site scripting vulnerability in home-assistant core, published on 27 Mar 2026. Any signed-in user can exploit it over the network, 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-33044 exists.

Affected packages and fixed versions:
- homeassistant (PyPI): affected from 2020.02; fixed in 2026.01
- homeassistant (PyPI): affected from 2020.02; fixed in 2026.01
- homeassistant (PyPI): affected from 2020.02; fixed in 2026.01

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

## Sources

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

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