# CVE-2025-62172: Home Assistant vulnerable to Stored XSS in Energy dashboard from Energy Entity Name > Authenticated attackers can inject malicious JavaScript into energy entity names, executing code in other users' sessions via dashboard tooltips. - **Severity:** High 8.5 (`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/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:** 14 Oct 2025 - **Updated:** 21 Oct 2025 - **Also known as:** GHSA-mq77-rv97-285m, PYSEC-2026-1453 ## What is CVE-2025-62172? CVE-2025-62172 is a high-severity cross-site scripting vulnerability in home-assistant core, published on 14 Oct 2025. 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. In versions 2025.1.0 through 2025.10.1, the energy dashboard is vulnerable to stored cross-site scripting. An authenticated user can inject malicious JavaScript code into an energy entity's name field, which is then executed when any user hovers over data points in the energy dashboard graph tooltips. The vulnerability exists because entity names containing HTML are not properly sanitized before being rendered in graph tooltips. This could allow an attacker with authentication to execute arbitrary JavaScript in the context of other users' sessions. Additionally, if an energy provider (such as Tibber) supplies a malicious default name for an entity, the vulnerability can be exploited without direct user action when the default name is used. This issue has been patched in version 2025.10.2. No known workarounds exist. Weakness: CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page), CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2025-62172? 3 open source packages ship an affected version, including homeassistant. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `homeassistant` | PyPI | From 2025.1.0 | 2025.10.2 | | `homeassistant` | PyPI | From 2025.1.0 | 2025.10.2 | | `homeassistant` | PyPI | From 2025.1.0 | 2025.10.2 | ## How do I fix CVE-2025-62172? Upgrade homeassistant to 2025.10.2 or later. ## Is CVE-2025-62172 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62172 exists. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-62172 and fix it if it is affected. What it is: CVE-2025-62172 is a high-severity cross-site scripting vulnerability in home-assistant core, published on 14 Oct 2025. 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-2025-62172 exists. Affected packages and fixed versions: - homeassistant (PyPI): affected from 2025.1.0; fixed in 2025.10.2 - homeassistant (PyPI): affected from 2025.1.0; fixed in 2025.10.2 - homeassistant (PyPI): affected from 2025.1.0; fixed in 2025.10.2 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-2025-62172/ (Markdown: https://insights.sbomify.com/CVE-2025-62172/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-62172 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-62172 - OSV: https://osv.dev/vulnerability/CVE-2025-62172 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-62172/ Summaries are generated and may contain mistakes; the official description above is the record.