CVE-2026-54317: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in home-assistant core
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 "via the access token from configuration." That promise is only half true. Write requests (POST and PUT) are handled by update_sensor(), which does check the request's Authorization: Bearer <token> header against the integration'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.
AI Analysis
Technical Summary
The Konnected integration in Home Assistant core registers an HTTP endpoint (KonnectedView) that does not require authentication for GET requests, despite comments suggesting access control via tokens. The update_sensor() method handling POST and PUT requests correctly verifies authorization tokens, but the get() method handling GET requests lacks any authentication checks. This results in exposure of sensitive information to unauthorized actors. The vulnerability is identified as CWE-200 (Exposure of Sensitive Information) and CWE-306 (Missing Authentication for Critical Function). It has a CVSS 3.1 base score of 7.6 (high severity) with attack vector as adjacent network, low attack complexity, no privileges required, no user interaction, and impacts confidentiality, integrity, and availability to varying degrees. The issue is fixed in Home Assistant core version 2026.6.0.
Potential Impact
Unauthorized actors can perform unauthenticated GET requests to the Konnected integration endpoint, potentially exposing sensitive information. Write operations remain protected by token-based authentication. The vulnerability impacts confidentiality (high), integrity (low), and availability (low) of the affected system.
Mitigation Recommendations
Upgrade Home Assistant core to version 2026.6.0 or later, where this vulnerability is fixed. No other mitigation or temporary workaround is indicated. Patch status is not explicitly stated but the fix is confirmed in version 2026.6.0.
CVE-2026-54317: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in home-assistant core
Description
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 "via the access token from configuration." That promise is only half true. Write requests (POST and PUT) are handled by update_sensor(), which does check the request's Authorization: Bearer <token> header against the integration'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.
CVSS v3.1
Score 7.6high
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Konnected integration in Home Assistant core registers an HTTP endpoint (KonnectedView) that does not require authentication for GET requests, despite comments suggesting access control via tokens. The update_sensor() method handling POST and PUT requests correctly verifies authorization tokens, but the get() method handling GET requests lacks any authentication checks. This results in exposure of sensitive information to unauthorized actors. The vulnerability is identified as CWE-200 (Exposure of Sensitive Information) and CWE-306 (Missing Authentication for Critical Function). It has a CVSS 3.1 base score of 7.6 (high severity) with attack vector as adjacent network, low attack complexity, no privileges required, no user interaction, and impacts confidentiality, integrity, and availability to varying degrees. The issue is fixed in Home Assistant core version 2026.6.0.
Potential Impact
Unauthorized actors can perform unauthenticated GET requests to the Konnected integration endpoint, potentially exposing sensitive information. Write operations remain protected by token-based authentication. The vulnerability impacts confidentiality (high), integrity (low), and availability (low) of the affected system.
Mitigation Recommendations
Upgrade Home Assistant core to version 2026.6.0 or later, where this vulnerability is fixed. No other mitigation or temporary workaround is indicated. Patch status is not explicitly stated but the fix is confirmed in version 2026.6.0.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-12T18:42:02.223Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a3acbe4eed863c81e6c9a5e
Added to database: 06/23/2026, 18:09:40 UTC
Last enriched: 06/30/2026, 22:58:09 UTC
Last updated: 08/07/2026, 12:41:12 UTC
Views: 53
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.