Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure user to open malicious URL in Companion app
-
DeliveryRender attacker iframe inside WebView
-
ExploitInvoke exposed externalApp/messageHandlers bridge
-
ExecutionInject JS via unsanitized callback identifier
-
PersistExecute in Home Assistant frontend origin
-
ImpactExfiltrate 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. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – 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
Affected Packages
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
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
Lifecycle Timeline
2DescriptionCVE.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
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.
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
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
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.
More in Home Assistant
View allhomeassistant is an open source home automation tool. Rated critical severity (CVSS 10.0), this vulnerability is remotel
Stored/DOM cross-site scripting in the Home Assistant frontend Statistics Graph card lets an authenticated user or a mal
Home Assistant Community Store (HACS) 1.10.0 contains a path traversal vulnerability that allows unauthenticated attacke
Home assistant is an open source home automation. Rated critical severity (CVSS 9.6), this vulnerability is remotely exp
Home assistant is an open source home automation. Rated critical severity (CVSS 9.6), this vulnerability is remotely exp
Path-traversal to remote code execution in Home Assistant Core before 2026.6.0 lets an authenticated user who can supply
Home Assistant before 2021.1.3 does not have a protection layer that can help to prevent directory-traversal attacks aga
Arbitrary file write in Home Assistant Core before 2026.6.0 lets unauthenticated attackers plant attacker-controlled fil
Home assistant is an open source home automation. Rated critical severity (CVSS 9.0), this vulnerability is remotely exp
The Home Assistant Companion for iOS and macOS app up to version 2023.4 are vulnerable to Client-Side Request Forgery. R
Stored cross-site scripting in the Home Assistant Energy dashboard (versions 2025.1.0 through 2025.10.1) lets an authent
Home Assistant is open source home automation software. Rated medium severity (CVSS 4.3), this vulnerability is no authe
EUVD-2026-33317
NVD
CVE.org
EPSS
Vulnrichment
GitHub
Exploit-DB