Home Assistant: Konnected alarm-panel switch state and zone topology disclosed to unauthenticated actors on the LAN
CVE-2026-54317GHSA-x84v-g949-293w
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (homeassistant 2026.6.0), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI homeassistant
- Affected
- < 2026.6.0
- Fixed in
- 2026.6.0
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-x84v-g949-293w lists affected ranges: PyPI homeassistant >=0 <2026.6.0 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-x84v-g949-293w lists affected ranges: PyPI homeassistant >=0 <2026.6.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 7.6 · CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
- EPSS
- CVE-2026-54317: 0.31% estimated exploitation activity in the next 30 days; percentile 23.70 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary The Konnected integration registers an HTTP endpoint, KonnectedView (homeassistant/components/konnected/init.py), that is marked as not requiring authentication (requiresauth = 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 updatesensor(), which does check the request's Authorization: Bearer <token header against the integration's stored access tokens (using hmac.comparedigest). - Read requests (GET) are handled by a separate get() method that has no authentication check at all. By sending GET requests to /api/konnected/device/{deviceid}?zone=N, any unauthenticated client on the LAN can: 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…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-x84v-g949-293w
- Revision 1 · created ·
Published from osv record GHSA-x84v-g949-293w
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-54317 Advisory: Home Assistant: Konnected alarm-panel switch state and zone topology disclosed to unauthenticated actors on the LAN IDs: CVE-2026-54317, GHSA-x84v-g949-293w Record: https://patchnext.com/advisories/cve-2026-54317 (revision 2, source checked 26 Oct 2026, 13:49 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.6) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: homeassistant 2026.6.0. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI homeassistant: affected < 2026.6.0; fixed in 2026.6.0 ## Suggested inspection (read-only) - `python -m pip show homeassistant`: prints the installed version. Run with the environment that serves production active. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on homeassistant. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-x84v-g949-293w (OSV record GHSA-x84v-g949-293w lists affected ranges: PyPI homeassistant >=0 <2026.6.0 (fixed)) - Verified: https://github.com/advisories/GHSA-x84v-g949-293w (GitHub-reviewed advisory GHSA-x84v-g949-293w lists affected ranges: PyPI homeassistant >=0 <2026.6.0) Commands are suggestions: review each one before running it.
Loading voting…