https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 07 Oct 2026 16:07:26 +0000 https://cve.radiocsirt.org/vuln/cve-2025-62172 <p><strong>Affected:</strong> home-assistant core</p> <p>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&#39;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&#39; 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.</p> <p><strong>Affected:</strong> home-assistant core</p> <p>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&#39;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&#39; 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.</p> https://cve.radiocsirt.org/vuln/cve-2025-62172 https://cve.radiocsirt.org/vuln/ghsa-mq77-rv97-285m <p><strong>Affected:</strong> PyPI: homeassistant</p> <p>### Summary An authenticated party can add a malicious name to the Energy entity, allowing for Cross-Site Scripting attacks against anyone who can see the Energy dashboard, when they hover over any information point (The blue bar in the picture below) &lt;img width=&#34;955&#34; height=&#34;568&#34; alt=&#34;1_cens&#34; src=&#34;https://github.com/user-attachments/assets/ed855216-c306-4b50-affc-cda100e72b74&#34; /&gt;</p> <p>An alternative, and more impactful scenario, is that the entity gets a malicious name from the provider of the Entity (in this case the energy provider: Tibber), and gets exploited that way, through the default name.</p> <p>### Details The incriminating entity in my scenario is from the Tibber integration, as shown in the screenshot below: &lt;img width=&#34;822&#34; height=&#34;309&#34; alt=&#34;2_cens&#34; src=&#34;https://github.com/user-attachments/assets/d0d5a7aa-8d0c-4dcb-825b-e4cb8ea8885b&#34; /&gt;</p> <p>The exploit should be possible regardless of the Energy integration, as the user can name the entity themselves and as such pick a malicious name. The default name given by the Energy integration can also be taken directly from their system, and be vulnerable that way. The execution happens within the energy dashboard, when hovering over a data point:</p> <p>&lt;img width=&#34;1545&#34; height=&#34;571&#34; alt=&#34;image&#34; src=&#34;https://github.com/user-attachments/assets/46dc7f00-4593-4271-8c3f-4c02b021ff2b&#34; /&gt;</p> <p>**Update found after issue was reported:** I found that the issue presents itself for any entity with a html-entity in the name, which is included and re…</p> <p><strong>Affected:</strong> PyPI: homeassistant</p> <p>### Summary An authenticated party can add a malicious name to the Energy entity, allowing for Cross-Site Scripting attacks against anyone who can see the Energy dashboard, when they hover over any information point (The blue bar in the picture below) &lt;img width=&#34;955&#34; height=&#34;568&#34; alt=&#34;1_cens&#34; src=&#34;https://github.com/user-attachments/assets/ed855216-c306-4b50-affc-cda100e72b74&#34; /&gt;</p> <p>An alternative, and more impactful scenario, is that the entity gets a malicious name from the provider of the Entity (in this case the energy provider: Tibber), and gets exploited that way, through the default name.</p> <p>### Details The incriminating entity in my scenario is from the Tibber integration, as shown in the screenshot below: &lt;img width=&#34;822&#34; height=&#34;309&#34; alt=&#34;2_cens&#34; src=&#34;https://github.com/user-attachments/assets/d0d5a7aa-8d0c-4dcb-825b-e4cb8ea8885b&#34; /&gt;</p> <p>The exploit should be possible regardless of the Energy integration, as the user can name the entity themselves and as such pick a malicious name. The default name given by the Energy integration can also be taken directly from their system, and be vulnerable that way. The execution happens within the energy dashboard, when hovering over a data point:</p> <p>&lt;img width=&#34;1545&#34; height=&#34;571&#34; alt=&#34;image&#34; src=&#34;https://github.com/user-attachments/assets/46dc7f00-4593-4271-8c3f-4c02b021ff2b&#34; /&gt;</p> <p>**Update found after issue was reported:** I found that the issue presents itself for any entity with a html-entity in the name, which is included and re…</p> https://cve.radiocsirt.org/vuln/ghsa-mq77-rv97-285m