How severe is CVE-2026-54318?

CVE-2026-54318 has a CVSS 3.x base score of 7.1, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.

Is CVE-2026-54318 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (2nd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-54318?

CVE-2026-54318 affects Home-assistant Home Assistant Companion. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-54318?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2026-54318 have an EU (EUVD) identifier?

Yes. CVE-2026-54318 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-38553.

When was CVE-2026-54318 published?

CVE-2026-54318 was published on 2026-06-23 and last updated on 2026-06-26.

CVE-2026-54318

CVE-2026-54318 is a high-severity vulnerability in Home-assistant Home Assistant Companion with a CVSS 3.x base score of 7.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-926.

Key facts

Severity: High (CVSS 3.x base score 7.1)
EPSS exploit prediction: 0% (2nd percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-38553
Weakness: CWE-926
Affected product: Home-assistant Home Assistant Companion
Published: 2026-06-23
Last modified: 2026-06-26

Description

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 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.

Frequently asked questions

What is CVE-2026-54318?: 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 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.
How severe is CVE-2026-54318?: CVE-2026-54318 has a CVSS 3.x base score of 7.1, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.
Is CVE-2026-54318 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (2nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-54318?: CVE-2026-54318 affects Home-assistant Home Assistant Companion. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-54318?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-54318 have an EU (EUVD) identifier?: Yes. CVE-2026-54318 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-38553.
When was CVE-2026-54318 published?: CVE-2026-54318 was published on 2026-06-23 and last updated on 2026-06-26.

References

Affected products (1)

cpe:2.3:a:home-assistant:home_assistant_companion:*:*:*:*:*:android:*:*

More vulnerabilities in Home-assistant Home Assistant Companion

CVE-2023-44385 — High (CVSS 8.6): The Home Assistant Companion for iOS and macOS app up to version 2023.4 are vulnerable to Client-Side Request Forgery.…
CVE-2023-41898 — High (CVSS 8.6): Home assistant is an open source home automation. The Home Assistant Companion for Android app up to version 2023.8.2…

All CVEs affecting Home-assistant Home Assistant Companion →

Other CWE-926 vulnerabilities

CVE-2025-5344 — High (CVSS 8.5): Bluebird devices contain a pre-loaded kiosk application. This application exposes an unsecured service provider…
CVE-2024-13917 — High (CVSS 8.3): An application "com.pri.applock", which is pre-loaded on Kruger&Matz smartphones, allows a user to encrypt any…
CVE-2025-68713 — High (CVSS 8.0): An issue was discovered in Rakuten Send Anywhere (File Transfer) for Android (com.estmob.android.sendanywhere) 23.2.9.…
CVE-2025-32347 — High (CVSS 7.8): In onStart of BiometricEnrollIntroduction.java, there is a possible way to determine the device's location due to an…
CVE-2021-25400 — High (CVSS 7.8): Intent redirection vulnerability in Samsung Internet prior to version 14.0.1.20 allows attacker to execute privileged…
CVE-2025-15464 — High (CVSS 7.5): Exported Activity allows external applications to gain application context and directly launch Gmail with inbox access,…

Browse all CWE-926 vulnerabilities →