Skip to content

CVE-2026-54317

Home-assistant authentication bypass

7.6 HIGHPublic exploitEPSS 0.31%
  1. Published23 Jun 2026

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 3.1 breakdown

Attack vectorAdjacent
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityLow
AvailabilityLow
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L

Affected products

Home-assistant< 2026.6.0

Remediation

Fixed in
Home-assistant≥ 2026.6.0

Frequently asked

Is CVE-2026-54317 being actively exploited?

CVE-2026-54317 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.31%.

How severe is CVE-2026-54317?

CVE-2026-54317 has a CVSS 3.1 base score of 7.6, rated high. EPSS estimates a 0.31% probability of exploitation.

Which products are affected by CVE-2026-54317?

Affected products include Home-assistant.

How do I fix CVE-2026-54317?

Upgrade affected software to a fixed version, for example Home-assistant 2026.6.0 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-54317 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.