CVE-2026-91130: Home Assistant Cross-Site Scripting Vulnerability

CRITICAL
Advisory Identifier: GHSA-wx4m-69m9-gx3m
CWE-80
Published
Advisory Summary

CVE-2026-91130 is a CRITICAL cross-site scripting vulnerability (CWE-80: Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS)) affecting Home Assistant libraries in the PyPI ecosystem. The issue involves xss in statistics graph card. Remediation is available by upgrading affected packages to version 2026.7.0.

CVE-2026-91130 at a Glance

CVE Identifier CVE-2026-91130
GHSA Identifier GHSA-wx4m-69m9-gx3m
Severity CRITICAL
CVSS v3.1 Base Score N/A
CWE Classification CWE-80: Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS)
Affected Product Home Assistant
Package Ecosystem PyPI
Published Date
Last Updated

How to Fix CVE-2026-91130

To remediate this vulnerability, upgrade all affected Home Assistant dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

homeassistant fixed: 2026.7.0
pip install homeassistant>=2026.7.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show homeassistant

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-91130, inspect your installed packages using pip:

pip show homeassistant

Analyze the terminal output to locate any version of Home Assistant in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2026.7.0), your application is affected.

Note: The pip show homeassistant command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-80: Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS), where the product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "<", ">", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages. In Home Assistant, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary An authenticated party can add a malicious name to any statistics-capable entity, allowing for Cross-Site Scripting attacks against anyone who views a Statistics Graph card containing that entity, when they hover over any data point on the chart. **Payload** <img width="1529" height="441" alt="image" src="https://github.com/user-attachments/assets/6926ce53-75fb-455a-bd4e-0c5281e8bed8" /> **Payload triggering** <img width="835" height="469" alt="image" src="https://github.com/user-attachments/assets/0bb9d17a-c123-4d44-8471-35097f65ddd2" /> An alternative, and more impactful scenario, is that the entity gets a malicious name from the provider of the integration (e.g. Tibber, Shelly, or any HACS integration), and is exploited that way through the default name — without requiring any direct access to the Home Assistant instance. This is the same supply-chain vector as CVE-2025-62172. ### Details The Statistics Graph card renders entity names in ECharts tooltips as raw HTML. The offending line is in `src/components/chart/statistics-chart.ts`: https://github.com/home-assistant/frontend/blob/c13a80ce5e7ae39f0262444e2b6295a074a96732/src/components/chart/statistics-chart.ts#L236 Where **_`param.seriesName`_** is interpolated verbatim into the returned HTML string: ``` return `${time}${param.marker} ${param.seriesName}: ${value}`; ``` No call to `filterXSS()` is made — unlike the Energy dashboard chart, which was patched as part of CVE-2025-62172: ``` // FIXED in energy-chart-options.ts:268 return `${param.marker} ${filterXSS(param.seriesName!)}: ...`; ``` The `statistics-chart` component was not updated when the Energy chart was patched, leaving the same class of vulnerability in place. The existing entity and payload used for CVE-2025-62172 is also a valid exploit for this vulnerability: <img width="962" height="500" alt="image" src="https://github.com/user-attachments/assets/35c84dcd-64d4-47b6-8df2-6c8b63cac880" /> The name value flows through the following chain: 1. `name` is set from `getStatisticLabel(this.hass, statistic_id, meta)`: https://github.com/home-assistant/frontend/blob/c13a80ce5e7ae39f0262444e2b6295a074a96732/src/components/chart/statistics-chart.ts#L411 2. `getStatisticLabel` is defined here and calls `computeStateName(entity)`: https://github.com/home-assistant/frontend/blob/c13a80ce5e7ae39f0262444e2b6295a074a96732/src/data/recorder.ts#L329-L339 3. `computeStateName` is defined here — no HTML encoding is applied: https://github.com/home-assistant/frontend/blob/c13a80ce5e7ae39f0262444e2b6295a074a96732/src/common/entity/compute_state_name.ts The only transformation applied to the name is replacing underscores with spaces (`computeObjectId(entityId).replace(/_/g, " ")`), which does not prevent HTML injection. **NB:** Do note that only the fields `Mean, State, Sum and Change` are vulnerable. The top 3 (Min, Max, Mean) or the bottom 3 (State, Sum, Change) are selected by default though, making it vulnerable by default: <img width="105" height="216" alt="image" src="https://github.com/user-attachments/assets/7a784c90-cca5-46da-bcb9-6942ad81da0c" /> Another requirement is that the Chart Type is of type Line, not Bar, which is also the default: <img width="133" height="91" alt="image" src="https://github.com/user-attachments/assets/4f131495-9000-4a80-808b-bf4be9f7a2f6" /> --- ### PoC 1. In **Settings → Devices & Services → Helpers**, click **+ Create Helper**. (For testing) 2. Choose **Template** → **Template sensor**. Fill in the form: - **Name:** `test <img src=x onerror=alert(document.domain) />` - **State template:** `{{0.00000001*as_timestamp(states('sensor.date_time_iso'))}}` - **Unit of measurement:** `kWh` - **State class:** `Measurement` - Click **Submit**. <img width="392" height="741" alt="image" src="https://github.com/user-attachments/assets/6a9b2c65-93fb-4d20-89b8-5a1f47a2bcb0" /> 3. Open a dashboard and add a **Statistics Graph** card targeting the new sensor: <img width="694" height="720" alt="image" src="https://github.com/user-attachments/assets/83996d12-d5ba-467a-9ca1-cbc46246ddff" /> **NB:** Set time-window to 5 minutes for ease of testing so you see data quickly 4. Hover over any data point on the chart. 5. The `onerror` handler fires — `alert(document.domain)` executes in the browser or HTML-injection appears depending on the payload ** Exact helper as described here** <img width="802" height="441" alt="image" src="https://github.com/user-attachments/assets/09284c10-bc39-410a-aff0-307e0bfd0502" /> **Own sensor** <img width="962" height="500" alt="image" src="https://github.com/user-attachments/assets/35c84dcd-64d4-47b6-8df2-6c8b63cac880" /> **Own sensor 2** <img width="835" height="469" alt="image" src="https://github.com/user-attachments/assets/0bb9d17a-c123-4d44-8471-35097f65ddd2" /> --- ### Impact The vulnerability can be exploited remotely via the supply-chain vector: any integration that automatically names entities (e.g. energy providers like Tibber) could deliver the payload without requiring the attacker to have any account on the target Home Assistant instance. This mirrors the exact attack path described in CVE-2025-62172. The most likely exploit is also through energy providers due to them providing multiple entities compatible with statistic graphs. Compared to CVE-2025-62172, this has the requirement that you add a Statistics Graph to your dashboard (or somehow view the entity in a Statistics Graph through other means, if such a method exists). Otherwise the attack flow is identical. Suggested 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 The root cause — missing `filterXSS()` on `param.seriesName` — is identical to the already-fixed Energy dashboard. The Statistics Graph card, which uses a shared `statistics-chart` component, was not included in the previous fix scope. Credit: Robin Lunde - [https://robinlunde.com](https://robinlunde.com)

CVE-2026-91130 Affected Home Assistant Versions

1 component(s)
Fixed Versions:
2026.7.0
Product / Package Ecosystem Affected Versions Fixed Version
homeassistant
PyPI
< 2026.7.0
2026.7.0

References

Frequently Asked Questions

What is CVE-2026-91130?
CVE-2026-91130 is a security vulnerability in Home Assistant involving XSS in Statistics Graph Card under CWE-80: Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS).
Which Home Assistant versions are affected?
Affected versions include releases prior to 2026.7.0 across affected packages: homeassistant.
What version fixes CVE-2026-91130?
Upgrading to 2026.7.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is homeassistant affected?
Yes, homeassistant is affected in releases prior to 2026.7.0. Upgrade your dependency to 2026.7.0 or later.
What CWE is associated with CVE-2026-91130?
CVE-2026-91130 is classified under CWE-80: Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) (The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "<", ">", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages.).
How can I check PyPI dependencies for CVE-2026-91130?
Run the dependency tree command: 'pip show homeassistant'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-wx4m-69m9-gx3m",
  "modified" : "2026-09-22T20:40:55Z",
  "published" : "2026-09-22T20:40:55Z",
  "aliases" : [ "CVE-2026-91130" ],
  "summary" : "Home Assistant: XSS in Statistics Graph Card",
  "details" : "### Summary\nAn authenticated party can add a malicious name to any statistics-capable entity, allowing for\nCross-Site Scripting attacks against anyone who views a Statistics Graph card containing that\nentity, when they hover over any data point on the chart.\n\n**Payload**\n<img width=\"1529\" height=\"441\" alt=\"image\" src=\"https://github.com/user-attachments/assets/6926ce53-75fb-455a-bd4e-0c5281e8bed8\" />\n\n**Payload triggering**\n<img width=\"835\" height=\"469\" alt=\"image\" src=\"https://github.com/user-attachments/assets/0bb9d17a-c123-4d44-8471-35097f65ddd2\" />\n\nAn alternative, and more impactful scenario, is that the entity gets a malicious name from the\nprovider of the integration (e.g. Tibber, Shelly, or any HACS integration), and is exploited\nthat way through the default name — without requiring any direct access to the Home Assistant\ninstance. This is the same supply-chain vector as CVE-2025-62172.\n\n\n### Details\n\nThe Statistics Graph card renders entity names in ECharts tooltips as raw HTML. The offending\nline is in `src/components/chart/statistics-chart.ts`:\n\nhttps://github.com/home-assistant/frontend/blob/c13a80ce5e7ae39f0262444e2b6295a074a96732/src/components/chart/statistics-chart.ts#L236\n\nWhere **_`param.seriesName`_** is interpolated verbatim into the returned HTML string:\n\n```\nreturn `${time}${param.marker} ${param.seriesName}: ${value}`;\n```\n\nNo call to `filterXSS()` is made — unlike the Energy dashboard chart, which was patched as part\nof CVE-2025-62172:\n\n```\n// FIXED in energy-chart-options.ts:268\nreturn `${param.marker} ${filterXSS(param.seriesName!)}: ...`;\n```\n\nThe `statistics-chart` component was not updated when the Energy chart was patched, leaving the\nsame class of vulnerability in place.\n\nThe existing entity and payload used for CVE-2025-62172 is also a valid exploit for this vulnerability:\n<img width=\"962\" height=\"500\" alt=\"image\" src=\"https://github.com/user-attachments/assets/35c84dcd-64d4-47b6-8df2-6c8b63cac880\" />\n\n\nThe name value flows through the following chain:\n\n1. `name` is set from `getStatisticLabel(this.hass, statistic_id, meta)`:\n   https://github.com/home-assistant/frontend/blob/c13a80ce5e7ae39f0262444e2b6295a074a96732/src/components/chart/statistics-chart.ts#L411\n\n2. `getStatisticLabel` is defined here and calls `computeStateName(entity)`:\n   https://github.com/home-assistant/frontend/blob/c13a80ce5e7ae39f0262444e2b6295a074a96732/src/data/recorder.ts#L329-L339\n\n3. `computeStateName` is defined here — no HTML encoding is applied:\n   https://github.com/home-assistant/frontend/blob/c13a80ce5e7ae39f0262444e2b6295a074a96732/src/common/entity/compute_state_name.ts\n\nThe only transformation applied to the name is replacing underscores with spaces\n(`computeObjectId(entityId).replace(/_/g, \" \")`), which does not prevent HTML injection.\n\n\n**NB:** Do note that only the fields `Mean, State, Sum and Change` are vulnerable. The top 3 (Min, Max, Mean) or the bottom 3 (State, Sum, Change) are selected by default though, making it vulnerable by default:\n<img width=\"105\" height=\"216\" alt=\"image\" src=\"https://github.com/user-attachments/assets/7a784c90-cca5-46da-bcb9-6942ad81da0c\" />\n\nAnother requirement is that the Chart Type is of type Line, not Bar, which is also the default:\n<img width=\"133\" height=\"91\" alt=\"image\" src=\"https://github.com/user-attachments/assets/4f131495-9000-4a80-808b-bf4be9f7a2f6\" />\n\n\n\n---\n\n### PoC\n\n1. In **Settings → Devices & Services → Helpers**, click **+ Create Helper**. (For testing)\n\n2. Choose **Template** → **Template sensor**. Fill in the form:\n   - **Name:** `test <img src=x onerror=alert(document.domain) />`\n   - **State template:** `{{0.00000001*as_timestamp(states('sensor.date_time_iso'))}}`\n   - **Unit of measurement:** `kWh`\n   - **State class:** `Measurement`\n   - Click **Submit**.\n\n<img width=\"392\" height=\"741\" alt=\"image\" src=\"https://github.com/user-attachments/assets/6a9b2c65-93fb-4d20-89b8-5a1f47a2bcb0\" />\n\n\n3. Open a dashboard and add a **Statistics Graph** card targeting the new sensor:\n\n\n<img width=\"694\" height=\"720\" alt=\"image\" src=\"https://github.com/user-attachments/assets/83996d12-d5ba-467a-9ca1-cbc46246ddff\" />\n\n**NB:** Set time-window to 5 minutes for ease of testing so you see data quickly\n\n\n4. Hover over any data point on the chart.\n\n\n\n\n5. The `onerror` handler fires — `alert(document.domain)` executes in the browser or HTML-injection appears depending on the payload\n\n\n** Exact helper as described here**\n<img width=\"802\" height=\"441\" alt=\"image\" src=\"https://github.com/user-attachments/assets/09284c10-bc39-410a-aff0-307e0bfd0502\" />\n\n**Own sensor**\n<img width=\"962\" height=\"500\" alt=\"image\" src=\"https://github.com/user-attachments/assets/35c84dcd-64d4-47b6-8df2-6c8b63cac880\" />\n\n**Own sensor 2**\n<img width=\"835\" height=\"469\" alt=\"image\" src=\"https://github.com/user-attachments/assets/0bb9d17a-c123-4d44-8471-35097f65ddd2\" />\n---\n\n### Impact\n\nThe vulnerability can be exploited remotely via the supply-chain vector: any integration that\nautomatically names entities (e.g. energy providers like Tibber) could deliver the payload\nwithout requiring the attacker to have any account on the target Home Assistant instance. This\nmirrors the exact attack path described in CVE-2025-62172. The most likely exploit is also through energy providers due to them providing multiple entities compatible with statistic graphs.\n\nCompared to CVE-2025-62172, this has the requirement that you add a Statistics Graph to your dashboard (or somehow view the entity in a Statistics Graph through other means, if such a method exists). Otherwise the attack flow is identical.\nSuggested 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\n\nThe root cause — missing `filterXSS()` on `param.seriesName` — is identical to the already-fixed\nEnergy dashboard. The Statistics Graph card, which uses a shared `statistics-chart` component,\nwas not included in the previous fix scope.\n\nCredit: Robin Lunde - [https://robinlunde.com](https://robinlunde.com)",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "homeassistant"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2026.7.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/home-assistant/core/security/advisories/GHSA-wx4m-69m9-gx3m"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/home-assistant/frontend/pull/52235"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/home-assistant/frontend/commit/b8c201b6d34414d30c622797366570185c219614"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/home-assistant/core"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/home-assistant/core/releases/tag/2026.7.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-80" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-22T20:40:55Z",
    "nvd_published_at" : null
  }
}