Summary
Home Assistant: XSS in Statistics Graph Card
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
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-91130? CVE-2026-91130 is a critical-severity security vulnerability in homeassistant (pip), affecting versions < 2026.7.0. It is fixed in 2026.7.0.
- Which versions of homeassistant are affected by CVE-2026-91130? homeassistant (pip) versions < 2026.7.0 is affected.
- Is there a fix for CVE-2026-91130? Yes. CVE-2026-91130 is fixed in 2026.7.0. Upgrade to this version or later.
- Is CVE-2026-91130 exploitable, and should I be worried? Whether CVE-2026-91130 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-91130 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-91130? Upgrade
homeassistantto 2026.7.0 or later.