# CVE-2025-62172: PYSEC-2026-1453 - Home Assistant has Stored XSS vulnerability in Energy dashboard from Energy Entity Name

Source: https://junglewise.ai/threats/cve-2025-62172-home-assistant-has-stored-xss-vulnerability-in-energy-dashboard  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2025-10-14  
License: CC BY 4.0 with a link back

CVE-2025-62172 · Severity: medium · CVSS 4 · Published 2025-10-14

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.

Technologies: [homeassistant (PyPI)](https://junglewise.ai/threats/technologies/homeassistant). Vendors: [PyPI](https://junglewise.ai/threats/vendors/pypi).

## Quick answers

**Is CVE-2025-62172 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2025-62172 being exploited in the wild.

**How severe is CVE-2025-62172?** Medium severity, with a CVSS score of 4, published 14 October 2025.

**Which products and versions are affected?** homeassistant (PyPI) ECOSYSTEM:introduced=2025.1.0,fixed=2025.10.2.

**Is there a fix for CVE-2025-62172?** Yes. homeassistant (PyPI): upgrade to 2025.10.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2025-62172?** Check whether you run homeassistant (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- homeassistant (PyPI): upgrade to 2025.10.2 or later

  ```sh
  pip install "homeassistant>=2025.10.2"
  ```


## Affected products

- homeassistant (PyPI) ECOSYSTEM:introduced=2025.1.0,fixed=2025.10.2

## Identifiers

- CVE-2025-62172
- GHSA-mq77-rv97-285m
- PYSEC-2026-1453

## Related threats

- [Home Assistant Statistics Graph Card XSS via entity names](https://junglewise.ai/threats/cve-2026-91130-home-assistant-statistics-graph-card-xss-via-entity-names)
- [Home Assistant Server-Side Request Forgery in mDNS IPP integration](https://junglewise.ai/threats/cve-2026-91129-home-assistant-server-side-request-forgery-in-mdns-ipp)
- [Home Assistant Core path traversal in backup upload](https://junglewise.ai/threats/cve-2026-64825-home-assistant-core-path-traversal-in-backup-upload)
- [PYSEC-2026-1452 - Home Assistant does not correctly validate SSL for outgoing requests in core and used libs](https://junglewise.ai/threats/cve-2025-25305-home-assistant-does-not-correctly-validate-ssl-for-outgoing)
- [PYSEC-2026-1451 - User accounts disclosed to unauthenticated actors on the LAN](https://junglewise.ai/threats/cve-2023-50715-user-accounts-disclosed-to-unauthenticated-actors-on-the-lan)