# Home Assistant: XSS in Statistics Graph Card

Advisory record · `GHSA-wx4m-69m9-gx3m`

- **Identifiers:** `GHSA-wx4m-69m9-gx3m` · `CVE-2026-91130` · `PYSEC-2026-4052`
- **State:** Confirmed
- **Severity:** CVSS 9.3 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-80](https://cwe.mitre.org/data/definitions/80.html)
- **Tags:** [Cross-site scripting (XSS)](https://agentprime.io/advisories/tag/xss.md)
- **Published:** 22 Sept 2026
- **Updated:** 1 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 22 Sept 2026, 20:40 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.3: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `homeassistant` (PyPI): affected `<2026.7.0`; fixed in `2026.7.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Home Assistant versions before 2026.7.0 are vulnerable to cross-site scripting in the Statistics Graph card. An authenticated user can give an entity a crafted name, or a name can come from an integration's provider, and the payload runs in the browser of anyone who views that entity on a Line-type Statistics Graph card and hovers over a data point. Upgrade to Home Assistant 2026.7.0 or later. No other workaround is given.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.3 Critical, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0048, the 42nd percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:09 UTC: First seen by agentprime
- 31 Oct 2026, 14:09 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-wx4m-69m9-gx3m)

## Sources

- [GitHub Advisory Database: GHSA-wx4m-69m9-gx3m](https://github.com/advisories/GHSA-wx4m-69m9-gx3m)
- [OSV: GHSA-wx4m-69m9-gx3m](https://osv.dev/vulnerability/GHSA-wx4m-69m9-gx3m)
- <https://github.com/home-assistant/core/security/advisories/GHSA-wx4m-69m9-gx3m>
- <https://github.com/home-assistant/frontend/pull/52235>
- <https://github.com/home-assistant/frontend/commit/b8c201b6d34414d30c622797366570185c219614>
- <https://github.com/home-assistant/core>
- <https://github.com/home-assistant/core/releases/tag/2026.7.0>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-wx4m-69m9-gx3m>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-wx4m-69m9-gx3m/>. Everything for agents: <https://agentprime.io/llms.txt>.
