Categories
CVE-2026-54317 high CVSS 7.6

Information Disclosure in homeassistant (CVE-2026-54317)

Summary

Vulnerability in homeassistant (CVE-2026-54317). Confidential information can be exposed externally. Exploitable via Authorization header. Mitigation: upgrade to 2026.6.0 or later.

Original description

The description as published by the source.

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 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.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-54317 has been found in homeassistant.
Attackers can target a specific entry point like Authorization header over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.6/10.
What to do: upgrade homeassistant to 2026.6.0 or later.
If unsure, ask your IT team or search "homeassistant CVE-2026-54317" on the vendor's site.

CVE-2026-54317 (homeassistant) — CWE-200 / CVSS v3 7.6
Attack vector: adjacent-network / unauthenticated / no user interaction
Attack surface: Authorization header / KonnectedView / hmac.compare_digest / device_id
Patched: 2026.6.0 — apply immediately
Workaround: Migrate to the EspHome integration, as suggested in the existing repair issue for the Konnected integration.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Information disclosure (CWE-200) exists in homeassistant. Attackers reach the vulnerable code path via Authorization header without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of homeassistant. Attack surface: Authorization header / KonnectedView / hmac.compare_digest / device_id.

🔥 Severity

Severity: High (CVSS 7.6/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 2026.6.0.

🛡️ Workaround

Workaround: Migrate to the EspHome integration, as suggested in the existing repair issue for the Konnected integration.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'homeassistant' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'homeassistant' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で homeassistant を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate
    Migrate to the EspHome integration, as suggested in the existing repair issue for the Konnected integration.

    パッチが適用されるまでの応急処置として、Migrate to the EspHome integration, as suggested in the existing repair issue for the Konnected integration. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch
    Upgrade homeassistant to 2026.6.0

    ステージング環境で 2026.6.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip homeassistant
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2026.6.0"}]}]
PyPI homeassistant
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2026.6.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details