https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 21 Oct 2026 12:51:30 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-10459 EUVD-2026-10459 https://cve.radiocsirt.org/vuln/euvd-2026-10459 https://cve.radiocsirt.org/vuln/fkie_cve-2023-50715 <p>Home Assistant is open source home automation software. Prior to version 2023.12.3, the login page discloses all active user accounts to any unauthenticated browsing request originating on the Local Area Network. Version 2023.12.3 contains a patch for this issue.</p> <p>When starting the Home Assistant 2023.12 release, the login page returns all currently active user accounts to browsing requests from the Local Area Network. Tests showed that this occurs when the request is not authenticated and the request originated locally, meaning on the Home Assistant host local subnet or any other private subnet. The rationale behind this is to make the login more user-friendly and an experience better aligned with other applications that have multiple user-profiles.</p> <p>However, as a result, all accounts are displayed regardless of them having logged in or not and for any device that navigates to the server. This disclosure is mitigated by the fact that it only occurs for requests originating from a LAN address. But note that this applies to the local subnet where Home Assistant resides and to any private subnet that can reach it.</p> <p>Home Assistant is open source home automation software. Prior to version 2023.12.3, the login page discloses all active user accounts to any unauthenticated browsing request originating on the Local Area Network. Version 2023.12.3 contains a patch for this issue.</p> <p>When starting the Home Assistant 2023.12 release, the login page returns all currently active user accounts to browsing requests from the Local Area Network. Tests showed that this occurs when the request is not authenticated and the request originated locally, meaning on the Home Assistant host local subnet or any other private subnet. The rationale behind this is to make the login more user-friendly and an experience better aligned with other applications that have multiple user-profiles.</p> <p>However, as a result, all accounts are displayed regardless of them having logged in or not and for any device that navigates to the server. This disclosure is mitigated by the fact that it only occurs for requests originating from a LAN address. But note that this applies to the local subnet where Home Assistant resides and to any private subnet that can reach it.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2023-50715 https://cve.radiocsirt.org/vuln/ghsa-jqpc-rc7g-vf83 <p><strong>Affected:</strong> PyPI: homeassistant</p> <p>### Summary</p> <p>The login page discloses all active user accounts to any unauthenticated browsing request originating on the Local Area Network.</p> <p>### Details</p> <p>Starting the [Home Assistant 2023.12 release](https://www.home-assistant.io/blog/2023/12/06/release-202312/), the login page returns all currently active user accounts to browsing requests from the Local Area Network. Tests showed that this occurs when:</p> <p>- The request is not authenticated and - The request originated locally, meaning on the Home Assistant host local subnet or any other private subnet (`10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, fd00::/8, ::ffff:10.0.0.0/104, ::ffff:172.16.0.0/108, ::ffff:192.168.0.0/112`)</p> <p>The rationale behind this is to make the login more user-friendly (see [release blog post](https://www.home-assistant.io/blog/2023/12/06/release-202312/)) and an experience better aligned with other applications that have multiple user-profiles.</p> <p>However, as a result, all accounts are displayed regardless of them having logged in or not and for any device that navigates to the server. This disclosure is mitigated by the fact that it only occurs for requests originating from a LAN address. But note that this applies to the local subnet where Home Assistant resides and to any private subnet that can reach it.</p> <p>### PoC</p> <p>1. Place a Home Assistant instance on a private subnet, i.e., 192.168.1.0/24. 2. Create a few users, let&#39;s say, three. 3. From any (or another) private subnet on the LAN, like 192.168.2.0/2…</p> <p><strong>Affected:</strong> PyPI: homeassistant</p> <p>### Summary</p> <p>The login page discloses all active user accounts to any unauthenticated browsing request originating on the Local Area Network.</p> <p>### Details</p> <p>Starting the [Home Assistant 2023.12 release](https://www.home-assistant.io/blog/2023/12/06/release-202312/), the login page returns all currently active user accounts to browsing requests from the Local Area Network. Tests showed that this occurs when:</p> <p>- The request is not authenticated and - The request originated locally, meaning on the Home Assistant host local subnet or any other private subnet (`10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, fd00::/8, ::ffff:10.0.0.0/104, ::ffff:172.16.0.0/108, ::ffff:192.168.0.0/112`)</p> <p>The rationale behind this is to make the login more user-friendly (see [release blog post](https://www.home-assistant.io/blog/2023/12/06/release-202312/)) and an experience better aligned with other applications that have multiple user-profiles.</p> <p>However, as a result, all accounts are displayed regardless of them having logged in or not and for any device that navigates to the server. This disclosure is mitigated by the fact that it only occurs for requests originating from a LAN address. But note that this applies to the local subnet where Home Assistant resides and to any private subnet that can reach it.</p> <p>### PoC</p> <p>1. Place a Home Assistant instance on a private subnet, i.e., 192.168.1.0/24. 2. Create a few users, let&#39;s say, three. 3. From any (or another) private subnet on the LAN, like 192.168.2.0/2…</p> https://cve.radiocsirt.org/vuln/ghsa-jqpc-rc7g-vf83 https://cve.radiocsirt.org/vuln/gsd-2023-50715 gsd-2023-50715 https://cve.radiocsirt.org/vuln/gsd-2023-50715 https://cve.radiocsirt.org/vuln/pysec-2026-1451 <p><strong>Affected:</strong> PyPI: homeassistant</p> <p>### Summary</p> <p>The login page discloses all active user accounts to any unauthenticated browsing request originating on the Local Area Network.</p> <p>### Details</p> <p>Starting the [Home Assistant 2023.12 release](https://www.home-assistant.io/blog/2023/12/06/release-202312/), the login page returns all currently active user accounts to browsing requests from the Local Area Network. Tests showed that this occurs when:</p> <p>- The request is not authenticated and - The request originated locally, meaning on the Home Assistant host local subnet or any other private subnet (`10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, fd00::/8, ::ffff:10.0.0.0/104, ::ffff:172.16.0.0/108, ::ffff:192.168.0.0/112`)</p> <p>The rationale behind this is to make the login more user-friendly (see [release blog post](https://www.home-assistant.io/blog/2023/12/06/release-202312/)) and an experience better aligned with other applications that have multiple user-profiles.</p> <p>However, as a result, all accounts are displayed regardless of them having logged in or not and for any device that navigates to the server. This disclosure is mitigated by the fact that it only occurs for requests originating from a LAN address. But note that this applies to the local subnet where Home Assistant resides and to any private subnet that can reach it.</p> <p>### PoC</p> <p>1. Place a Home Assistant instance on a private subnet, i.e., 192.168.1.0/24. 2. Create a few users, let&#39;s say, three. 3. From any (or another) private subnet on the LAN, like 192.168.2.0/2…</p> <p><strong>Affected:</strong> PyPI: homeassistant</p> <p>### Summary</p> <p>The login page discloses all active user accounts to any unauthenticated browsing request originating on the Local Area Network.</p> <p>### Details</p> <p>Starting the [Home Assistant 2023.12 release](https://www.home-assistant.io/blog/2023/12/06/release-202312/), the login page returns all currently active user accounts to browsing requests from the Local Area Network. Tests showed that this occurs when:</p> <p>- The request is not authenticated and - The request originated locally, meaning on the Home Assistant host local subnet or any other private subnet (`10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, fd00::/8, ::ffff:10.0.0.0/104, ::ffff:172.16.0.0/108, ::ffff:192.168.0.0/112`)</p> <p>The rationale behind this is to make the login more user-friendly (see [release blog post](https://www.home-assistant.io/blog/2023/12/06/release-202312/)) and an experience better aligned with other applications that have multiple user-profiles.</p> <p>However, as a result, all accounts are displayed regardless of them having logged in or not and for any device that navigates to the server. This disclosure is mitigated by the fact that it only occurs for requests originating from a LAN address. But note that this applies to the local subnet where Home Assistant resides and to any private subnet that can reach it.</p> <p>### PoC</p> <p>1. Place a Home Assistant instance on a private subnet, i.e., 192.168.1.0/24. 2. Create a few users, let&#39;s say, three. 3. From any (or another) private subnet on the LAN, like 192.168.2.0/2…</p> https://cve.radiocsirt.org/vuln/pysec-2026-1451