<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 23:50:29 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-54317 — Home Assistant: Konnected alarm-panel switch state and zone topology disclosed to unauthenticated actors on the LAN</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-54317</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; home-assistant core&lt;/p&gt;
&lt;p&gt;Home Assistant is open source home automation software that puts local control and privacy first. Prior to 2026.6.0, the Konnected integration registers an HTTP endpoint, KonnectedView (homeassistant/components/konnected/__init__.py), that is marked as not requiring authentication (requires_auth = False). A comment next to that line says auth is instead handled &amp;#34;via the access token from configuration.&amp;#34; That promise is only half true. Write requests (POST and PUT) are handled by update_sensor(), which does check the request&amp;#39;s Authorization: Bearer &amp;lt;token&amp;gt; header against the integration&amp;#39;s stored access tokens (using hmac.compare_digest). Read requests (GET) are handled by a separate get() method that has no authentication check at all. This vulnerability is fixed in 2026.6.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; home-assistant core&lt;/p&gt;
&lt;p&gt;Home Assistant is open source home automation software that puts local control and privacy first. Prior to 2026.6.0, the Konnected integration registers an HTTP endpoint, KonnectedView (homeassistant/components/konnected/__init__.py), that is marked as not requiring authentication (requires_auth = False). A comment next to that line says auth is instead handled &amp;#34;via the access token from configuration.&amp;#34; That promise is only half true. Write requests (POST and PUT) are handled by update_sensor(), which does check the request&amp;#39;s Authorization: Bearer &amp;lt;token&amp;gt; header against the integration&amp;#39;s stored access tokens (using hmac.compare_digest). Read requests (GET) are handled by a separate get() method that has no authentication check at all. This vulnerability is fixed in 2026.6.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-54317</guid>
    </item>
    <item>
      <title>GHSA-x84v-g949-293w — Home Assistant: Konnected alarm-panel switch state and zone topology disclosed to unauthenticated actors on the LAN</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-x84v-g949-293w</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: homeassistant&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The Konnected integration registers an HTTP endpoint, `KonnectedView` (`homeassistant/components/konnected/__init__.py`), that is marked as **not requiring authentication** (`requires_auth = False`). A comment next to that line says auth is instead handled &amp;#34;via the access token from configuration.&amp;#34;&lt;/p&gt;
&lt;p&gt;That promise is only half true:&lt;/p&gt;
&lt;p&gt;- **Write requests (POST and PUT)** are handled by `update_sensor()`, which *does* check the request&amp;#39;s `Authorization: Bearer &amp;lt;token&amp;gt;` header against the integration&amp;#39;s stored access tokens (using `hmac.compare_digest`).
- **Read requests (GET)** are handled by a separate `get()` method that has **no authentication check at all.**&lt;/p&gt;
&lt;p&gt;By sending GET requests to `/api/konnected/device/{device_id}?zone=N`, any unauthenticated client on the LAN can:&lt;/p&gt;
&lt;p&gt;1. **Enumerate configured Konnected device IDs** — the endpoint returns a clean 404-vs-200 difference that acts as an oracle for which devices exist.
2. **Read switch output states** — the on/off state of every switch output (siren, strobe, and relay outputs of the alarm panel).
3. **Read the panel&amp;#39;s zone topology** — how the alarm panel&amp;#39;s zones are configured.
4. **Trigger panel connections** — each unauthenticated GET forces one outbound `panel.async_connect()` call to the Konnected hardware on the LAN.&lt;/p&gt;
&lt;p&gt;The same URL that correctly rejects unauthenticated POST and PUT requests silently serves unauthenticated GET requests, leaking alarm-panel state and device topology to anyone who can reach Ho…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: homeassistant&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The Konnected integration registers an HTTP endpoint, `KonnectedView` (`homeassistant/components/konnected/__init__.py`), that is marked as **not requiring authentication** (`requires_auth = False`). A comment next to that line says auth is instead handled &amp;#34;via the access token from configuration.&amp;#34;&lt;/p&gt;
&lt;p&gt;That promise is only half true:&lt;/p&gt;
&lt;p&gt;- **Write requests (POST and PUT)** are handled by `update_sensor()`, which *does* check the request&amp;#39;s `Authorization: Bearer &amp;lt;token&amp;gt;` header against the integration&amp;#39;s stored access tokens (using `hmac.compare_digest`).
- **Read requests (GET)** are handled by a separate `get()` method that has **no authentication check at all.**&lt;/p&gt;
&lt;p&gt;By sending GET requests to `/api/konnected/device/{device_id}?zone=N`, any unauthenticated client on the LAN can:&lt;/p&gt;
&lt;p&gt;1. **Enumerate configured Konnected device IDs** — the endpoint returns a clean 404-vs-200 difference that acts as an oracle for which devices exist.
2. **Read switch output states** — the on/off state of every switch output (siren, strobe, and relay outputs of the alarm panel).
3. **Read the panel&amp;#39;s zone topology** — how the alarm panel&amp;#39;s zones are configured.
4. **Trigger panel connections** — each unauthenticated GET forces one outbound `panel.async_connect()` call to the Konnected hardware on the LAN.&lt;/p&gt;
&lt;p&gt;The same URL that correctly rejects unauthenticated POST and PUT requests silently serves unauthenticated GET requests, leaking alarm-panel state and device topology to anyone who can reach Ho…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-x84v-g949-293w</guid>
    </item>
  </channel>
</rss>
