CVE-2026-54318
Home-Assistant Home Assistant Companion ≤ 2026.5.3
Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:NSummary
CVE-2026-54318 is a high-severity Improper Export of Android Application Components (CWE-926) vulnerability in Home-Assistant Home Assistant Companion. Its CVSS base score is 7.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Inter-Process Communication (T1559); ranked at the 4th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-38553
Vulnerability Data
Home Assistant is open source home automation software that puts local control and privacy first. Prior to 2026.5.3, the LocationSensorManager BroadcastReceiver is exported with no permission. Any installed app, with zero runtime permissions, can broadcast a forged Google Play Services…
more
LocationResult directly to it; the receiver trusts the extra and forwards it to the user's Home Assistant server as the device's real location. This bypasses Android's developer-mode "Mock Location" gate and allows a local malicious app to drive zone-based automations (unlock door / disarm alarm / open garage) by faking the user's GPS position. This vulnerability is fixed in 2026.5.3.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
AC-3 directly requires enforcement of authorizations on logical access, which stops an exported Android component from being reachable without proper restrictions.
Least privilege reduces the exposure of exported components by limiting unnecessary authorizations granted to other apps.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure-coding standards require explicit permission declarations and intent-filter restrictions to avoid improper exports.
Security testing can detect exported components lacking proper restrictions, providing partial coverage of the weakness.
Enforcing information-access restrictions on exported Android components directly prevents unauthorized launch or data access.
Defining application security requirements includes specifying proper export restrictions and permission checks for components.
Secure architecture principles discourage overly permissive component exports, though the control is broader than this single weakness.