Skip to main content

Home Assistant Companion EUVDEUVD-2026-33317

| CVE-2026-44698 HIGH
Code Injection (CWE-94)
2026-05-29 GitHub_M
8.3
CVSS 3.1 · Vendor: GitHub_M
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Lure user to open malicious URL in Companion app
  2. Delivery
    Render attacker iframe inside WebView
  3. Exploit
    Invoke exposed externalApp/messageHandlers bridge
  4. Execution
    Inject JS via unsanitized callback identifier
  5. Persist
    Execute in Home Assistant frontend origin
  6. Impact
    Exfiltrate access token to attacker server

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the victim to open content inside the Home Assistant Companion app's WebView that loads an attacker-controlled cross-origin iframe - typically via an iframe card, webpage card, or other custom Lovelace resource pointing at attacker content, or a link clicked from within the app - and the device must be running a vulnerable Companion App version (iOS < 2026.4.1 or Android < 2026.4.4) with the user already signed in so a valid access token exists to steal. Limiting factors per CVSS AV:N/AC:H/PR:N/UI:R: no authentication to the attacker's content is needed, but high attack complexity reflects the need to get the malicious iframe rendered in the Companion WebView specifically (not the system browser, where the bridge is absent), and user interaction is required to load the trigger dashboard or link; desktop/browser-only users of Home Assistant are not affected.

Impact

CVSS 8.3 (High) is driven by Scope:Changed plus full CIA impact, reflecting the fact that an untrusted iframe origin can pivot into the Home Assistant frontend origin and exfiltrate long-lived access tokens - a token theft outcome with material downstream risk for smart-home control. However, attack complexity is High (AC:H) and user interaction is required (UI:R): exploitation depends on the victim using the Companion app to navigate to, or render content from, an attacker-controlled page that loads a malicious iframe, and on the Lovelace/dashboard configuration permitting such embedding. EPSS and CISA KEV status are not provided in the input, and no public POC is referenced, so this should currently be treated as a credible high-severity client-side issue rather than a mass-exploitation event - patch promptly, but it is not on par with an unauthenticated server-side RCE. The CWE-94 classification is appropriate; the network attack vector is consistent with the description because the malicious frame is delivered over the network into a WebView.

Exploit ScenarioDerived

A Home Assistant user opens a dashboard inside the Companion app that contains (or is tricked via a link/notification into loading) an attacker-controlled webpage or iframe card. The malicious frame calls the exposed bridge (window.externalApp.getExternalAuth on Android or webkit.messageHandlers.getExternalAuth on iOS) with a poisoned callback identifier that, when interpolated back into the main frame, executes attacker JavaScript in the Home Assistant frontend origin and POSTs the user's access token to an external server. No public POC is referenced.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – May 29, 2026

Cross-origin JavaScript injection in Home Assistant Companion apps for Android (before 2026.4.4) and iOS (before 2026.4.1) allows a malicious iframe loaded inside the app's WebView to execute arbitrary JavaScript in the Home Assistant frontend's origin and steal the signed-in user's access token. The flaw stems from exposing the native JavaScript bridge (window.externalApp on Android, webkit.messageHandlers.getExternalAuth on iOS) to all frames combined with unsanitized callback identifier interpolation. No public exploit identified at time of analysis, and the issue is not in CISA KEV.

RemediationAI

Vendor-released patches are available: upgrade the iOS Companion App to 2026.4.1 or later and the Android Companion App to 2026.4.4 or later via the App Store and Google Play, per the GitHub Security Advisory at https://github.com/home-assistant/core/security/advisories/GHSA-7jp2-p2fw-mgvf. Until users update, administrators should avoid embedding untrusted third-party content (webpage cards, iframe cards, custom Lovelace resources from unknown sources) in dashboards that are opened inside the Companion app, since the bridge is exposed to all frames - note this disables legitimate iframe/webpage integrations as a side effect. After patching, rotate or revoke long-lived access tokens issued to mobile users in case tokens were previously exfiltrated, accepting that this forces re-authentication on all client devices.

Affected VersionsENISA

core < 2026.4.4
Companion app (Android) < 2026.4.4
Companion app (iOS) < 2026.4.1

Affected Packages

euvd companion_app_android fix: 2026.4.4
euvd companion_app_ios fix: 2026.4.1
euvd core fix: 2026.4.4

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 3 packages in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability sits in the JavaScript bridge that the Companion apps inject into the in-app WKWebView (iOS) and Android WebView to give the Home Assistant frontend access to native capabilities such as authentication token retrieval (getExternalAuth/revokeExternalAuth) and event passing (externalBus). Two compounding defects map to CWE-94 (Improper Control of Generation of Code, i.e., code injection): first, the bridge handlers were attached without origin or frame isolation, so any nested or cross-origin iframe rendered inside the Companion app's WebView could invoke them; second, the callback identifier supplied by the JS caller was interpolated directly into the JavaScript executed back in the main frame, letting an attacker break out of the expected callback name and emit arbitrary code into the parent (home-assistant.io / local Home Assistant) origin. CPE strings indicate both the iOS Companion App (cpe:2.3:a:home_assistant:companion_app_(ios)) and Android Companion App (cpe:2.3:a:home_assistant:companion_app_(android)) packages are affected, with Home Assistant core (cpe:2.3:a:home-assistant:core) also enumerated as a related component.

Know when Home Assistant gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (GitHub_M) PRIMARY 8.3 HIGH
AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

Primary rating from Vendor (GitHub_M) · only source for this CVE.

CVSS VectorVendor: GitHub_M

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch available
May 29, 2026 - 15:01 EUVD
CVE Published
May 29, 2026 - 13:32 nvd
HIGH 8.3

DescriptionCVE.org

Home Assistant is open source home automation software that puts local control and privacy first. Prior to 2026.4.1 for iOS and 2026.4.4 for Android, he Home Assistant Companion apps for Android and iOS expose a JavaScript bridge to the in-app WebView window.externalApp on Android and webkit.messageHandlers.getExternalAuth (alongside revokeExternalAuth and externalBus) on iOS. Two flaws expose the bridge to all frames (including cross-origin iframes) and unsanitized interpolation of the JavaScript callback identifier allows a cross-origin iframe rendered inside the Companion app to execute arbitrary JavaScript in the Home Assistant frontend's main-frame origin and exfiltrate the signed-in user's access token. This vulnerability is fixed in 2026.4.1 for iOS and 2026.4.4 for Android.

Executive ViewAI

Why It Matters

Home Assistant Companion mobile apps (Android and iOS) are vulnerable to token theft attacks that could grant unauthorized access to users' smart home and IoT systems. Attackers could control connected devices, change settings, or access sensitive home automation data through a malicious link or webpage viewed within the app. Any organization managing IoT devices through Home Assistant should assess exposure and prepare for remediation.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include: (1) restricting Companion app access to trusted networks only; (2) continuous monitoring of authentication logs for unusual token usage; (3) educating users to avoid clicking untrusted links while logged into the app; (4) if technically feasible, disabling or restricting iframe functionality in the app's WebView. These are temporary measures only. Deployment of Home Assistant Companion versions 2026.4.4+ (Android) and 2026.4.1+ (iOS) is mandatory once available.

Threat Intelligence Overview

EPSS Score
0.0%
Top 95% exploitable
Social Media
2
Sightings
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

42
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +42
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Code Injection CRITICAL

Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

CVE-2023-27482 CRITICAL POC
10.0 Mar 08

homeassistant is an open source home automation tool. Rated critical severity (CVSS 10.0), this vulnerability is remotel

CVE-2026-91130 CRITICAL POC
9.3 Sep 22

Stored/DOM cross-site scripting in the Home Assistant frontend Statistics Graph card lets an authenticated user or a mal

CVE-2021-47942 HIGH POC
8.7 May 16

Home Assistant Community Store (HACS) 1.10.0 contains a path traversal vulnerability that allows unauthenticated attacke

CVE-2023-41897 CRITICAL
9.6 Oct 19

Home assistant is an open source home automation. Rated critical severity (CVSS 9.6), this vulnerability is remotely exp

CVE-2023-41895 CRITICAL
9.6 Oct 19

Home assistant is an open source home automation. Rated critical severity (CVSS 9.6), this vulnerability is remotely exp

CVE-2026-64824 CRITICAL
9.3 Jul 21

Path-traversal to remote code execution in Home Assistant Core before 2026.6.0 lets an authenticated user who can supply

CVE-2021-3152 MEDIUM POC
5.3 Jan 26

Home Assistant before 2021.1.3 does not have a protection layer that can help to prevent directory-traversal attacks aga

CVE-2026-64825 CRITICAL
9.0 Jul 21

Arbitrary file write in Home Assistant Core before 2026.6.0 lets unauthenticated attackers plant attacker-controlled fil

CVE-2023-41896 CRITICAL
9.0 Oct 19

Home assistant is an open source home automation. Rated critical severity (CVSS 9.0), this vulnerability is remotely exp

CVE-2023-44385 HIGH
8.8 Oct 19

The Home Assistant Companion for iOS and macOS app up to version 2023.4 are vulnerable to Client-Side Request Forgery. R

CVE-2025-62172 HIGH
8.5 Oct 14

Stored cross-site scripting in the Home Assistant Energy dashboard (versions 2025.1.0 through 2025.10.1) lets an authent

CVE-2023-50715 MEDIUM POC
4.3 Dec 15

Home Assistant is open source home automation software. Rated medium severity (CVSS 4.3), this vulnerability is no authe

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy