# CVE-2026-54317: Home Assistant: Konnected alarm-panel switch state and zone topology disclosed to unauthenticated actors on the LAN


- **Severity:** High 7.6 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Jun 2026
- **Updated:** 26 Jun 2026
- **Also known as:** GHSA-x84v-g949-293w, PYSEC-2026-241

## What is CVE-2026-54317?

CVE-2026-54317 is a high-severity vulnerability in home-assistant core, published on 23 Jun 2026. 

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

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-54317?

3 open source packages ship an affected version, including homeassistant. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `homeassistant` | PyPI | All versions | 2026.6.0 |
| `homeassistant` | PyPI | All versions | 2026.6.0 |
| `homeassistant` | PyPI | All versions | 2026.6.0 |

Products: Home-Assistant Home-Assistant.

## How do I fix CVE-2026-54317?

Upgrade homeassistant to 2026.6.0 or later.

## Is CVE-2026-54317 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54317 exists.

## Other vulnerabilities in home-assistant core

- [CVE-2023-27482](https://insights.sbomify.com/CVE-2023-27482/): Auth bypass in core (critical 10.0)
- [CVE-2023-41895](https://insights.sbomify.com/CVE-2023-41895/): Cross-site Scripting via auth_callback login in Home Assistant Core (high 8.8)
- [CVE-2023-41897](https://insights.sbomify.com/CVE-2023-41897/): Lack of XFO header allows clickjacking in Home Assistant Core (high 8.8)
- [CVE-2020-36517](https://insights.sbomify.com/CVE-2020-36517/): Information disclosure in n/a (high 7.5)
- [CVE-2018-21019](https://insights.sbomify.com/CVE-2018-21019/): Home Assistant information disclosure vulnerability (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54317 and fix it if it is affected.

What it is: CVE-2026-54317 is a high-severity vulnerability in home-assistant core, published on 23 Jun 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54317 exists.

Affected packages and fixed versions:
- homeassistant (PyPI): affected all versions; fixed in 2026.6.0
- homeassistant (PyPI): affected all versions; fixed in 2026.6.0
- homeassistant (PyPI): affected all versions; fixed in 2026.6.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54317/ (Markdown: https://insights.sbomify.com/CVE-2026-54317/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54317
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54317
- OSV: https://osv.dev/vulnerability/CVE-2026-54317

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54317/
Summaries are generated and may contain mistakes; the official description above is the record.