Read the docs
TI-2023-22285 Aliases CVE-2023-41893GHSA-qhhj-7hrc-gqj5

Account takeover via auth_callback login in Home Assistant Core

Priority LOW 25CWE-200Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
Required
Attack complexity
Low
Impact type
Information disclosure
Confidentiality · integrity · availability
Low · Low · None
Fix status
Fixed

Attack profile from CVSS 3.1 · NVD. Fix status from CNA and GitHub. Impact type from CWE-200.

Summary

Home assistant is an open source home automation. The audit team’s analyses confirmed that the `redirect_uri` and `client_id` are alterable when logging in. Consequently, the code parameter utilized to fetch the `access_token` post-authentication will be sent to the URL specified in the aforementioned parameters. Since an arbitrary URL is permitted and `homeassistant.local` represents the preferred, default domain likely used and trusted by many users, an attacker could leverage this weakness to manipulate a user and retrieve account access. Notably, this attack strategy is plausible if the victim has exposed their Home Assistant to the Internet, since after acquiring the victim’s `access_token` the adversary would need to utilize it directly towards the instance to achieve any pertinent malicious actions. To achieve this compromise attempt, the attacker must send a link with a `redirect_uri` that they control to the victim’s own Home Assistant instance. In the eventuality the victim authenticates via said link, the attacker would obtain code sent to the specified URL in `redirect_uri`, which can then be leveraged to fetch an `access_token`. Pertinently, an attacker could increase the efficacy of this strategy by registering a near identical domain to `homeassistant.local`, which at first glance may appear legitimate and thereby obfuscate any malicious intentions. This issue has been addressed in version 2023.9.0 and all users are advised to upgrade. There are no known workarounds for this vulnerability.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00452 39th percentileScored 2026-11-07
Fix Fixed core (home-assistant): 2023.9.0homeassistant (PyPI): 2023.9.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
home-assistantcorebefore 2023.9.02023.9.0Patch availableCNA
—homeassistant (PyPI)before 2023.9.02023.9.0Patch availableGHSA-qhhj-7hrc-gqj5
  • core Vendorhome-assistant Affected before 2023.9.0 Fixed in 2023.9.0 Patch available CNA
  • homeassistant (PyPI) Vendor— Affected before 2023.9.0 Fixed in 2023.9.0 Patch available GHSA-qhhj-7hrc-gqj5

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:home-assistant:home-assistant:*:*:*:*:*:*:*:*before 2023.9.0Vulnerablehome-assistant
  • cpe:2.3:a:home-assistant:home-assistant:*:*:*:*:*:*:*:* Versions before 2023.9.0 Vulnerable ·home-assistant

Remediation

  • Fix · CNA core (home-assistant) Fixed in 2023.9.0
  • Fix · GHSA-qhhj-7hrc-gqj5 homeassistant (PyPI) Fixed in 2023.9.0 Advisory →

Timeline

  1. 2026-10-02 Threatist record created from CVE-2023-41893
  2. 2026-10-03 Alias added: GHSA-qhhj-7hrc-gqj5

References

  • TI-2023-12210 Improper authentication in home-assistant core CVSS 3.1CRITICAL 10.0
  • TI-2026-25491 Home Assistant has stored XSS in history-graphs CVSS 4.0HIGH 7.3
  • TI-2026-25490 Home Assistant has stored XSS in Map-card through malicious device name CVSS 4.0HIGH 7.3
  • TI-2026-39212 Home Assistant: Konnected alarm-panel switch state and zone topology disclosed to unauthenticated actors on the LAN CVSS 3.1HIGH 7.6
  • TI-2025-40423 Home Assistant Core before v2025.8.0 is vulnerable to Directory Traversal. CVSS 3.1MEDIUM 4.0
  • TI-2023-22289 Lack of XFO header allows clickjacking in Home Assistant Core CVSS 3.1CRITICAL 9.6
See all 15 →

Sources