CVE-2026-54318

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 98% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.1
EG Score
7.1(medium)
EPSS
1.7%
KEV
Not listed

Published

June 23, 2026

Last Modified

June 26, 2026

Advisory Details (2)

Auto-updated Jun 23, 2026
Patch available. Sources: github_pr, github.
github Patch Available

Exported BroadcastReceiver allows local apps to spoof device location · Advisory · home-assistant/core · GitHub

https://github.com/home-assistant/core/security/advisories/GHSA-77r5-pw5w-mgj3
github_pr

Introduce RequestAccurateLocationReceiver and restrict LocationSensorManager export

Fix merged in home-assistant/android PR #6837 on 2026-05-11 — awaiting tagged release

https://github.com/home-assistant/android/pull/6837

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 27× in last 7d / 58× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 20:44 UTCEG score recompute
  2. 2026-07-11 08:27 UTCEPSS rescore
  3. 2026-07-11 08:27 UTCEPSS rescore
  4. 2026-07-11 07:38 UTCEG score recompute
  5. 2026-07-10 18:30 UTCEG score recompute
  6. 2026-07-10 05:20 UTCEG score recompute
  7. 2026-07-09 19:10 UTCEPSS rescore
  8. 2026-07-09 19:10 UTCEPSS rescore
  9. 2026-07-09 16:07 UTCEG score recompute
  10. 2026-07-09 02:59 UTCEG score recompute
  11. 2026-07-08 15:16 UTCEPSS rescore
  12. 2026-07-08 15:16 UTCEPSS rescore
  13. 2026-07-08 13:54 UTCEG score recompute
  14. 2026-07-08 00:43 UTCEG score recompute
  15. 2026-07-07 13:46 UTCEPSS rescore
  16. 2026-07-07 13:46 UTCEPSS rescore
  17. 2026-07-07 11:38 UTCEG score recompute
  18. 2026-07-06 22:32 UTCEG score recompute
  19. 2026-07-06 16:27 UTCEPSS rescore
  20. 2026-07-06 16:27 UTCEPSS rescore
  21. 2026-07-06 09:27 UTCEG score recompute
  22. 2026-07-06 02:23 UTCEPSS rescore
  23. 2026-07-06 02:23 UTCEPSS rescore
  24. 2026-07-05 19:48 UTCEG score recompute
  25. 2026-07-05 06:43 UTCEG score recompute
Show 33 more
  1. 2026-07-05 02:31 UTCEPSS rescore
  2. 2026-07-05 02:30 UTCEPSS rescore
  3. 2026-07-04 17:29 UTCEG score recompute
  4. 2026-07-04 06:31 UTCEPSS rescore
  5. 2026-07-04 06:31 UTCEPSS rescore
  6. 2026-07-04 04:23 UTCEG score recompute
  7. 2026-07-03 15:16 UTCEG score recompute
  8. 2026-07-03 02:10 UTCEG score recompute
  9. 2026-07-02 13:05 UTCEG score recompute
  10. 2026-07-01 23:58 UTCEG score recompute
  11. 2026-07-01 10:53 UTCEG score recompute
  12. 2026-06-30 23:22 UTCEPSS rescore
  13. 2026-06-30 21:48 UTCEG score recompute
  14. 2026-06-30 08:42 UTCEG score recompute
  15. 2026-06-29 19:37 UTCEG score recompute
  16. 2026-06-29 06:31 UTCEG score recompute
  17. 2026-06-28 17:26 UTCEG score recompute
  18. 2026-06-28 14:07 UTCEPSS rescore
  19. 2026-06-28 04:56 UTCEPSS rescore
  20. 2026-06-28 04:56 UTCEPSS rescore
  21. 2026-06-28 04:20 UTCEG score recompute
  22. 2026-06-27 15:14 UTCEG score recompute
  23. 2026-06-27 03:08 UTCEPSS rescore
  24. 2026-06-27 02:09 UTCEG score recompute
  25. 2026-06-26 13:03 UTCEG score recompute
  26. 2026-06-25 23:59 UTCEG score recompute
  27. 2026-06-25 13:49 UTCEPSS rescore
  28. 2026-06-25 10:51 UTCEG score recompute
  29. 2026-06-24 21:45 UTCEG score recompute
  30. 2026-06-24 14:05 UTCEPSS rescore
  31. 2026-06-24 08:40 UTCEG score recompute
  32. 2026-06-23 19:34 UTCEG score recompute
  33. 2026-06-23 19:32 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-54318?
CVE-2026-54318 is a high vulnerability published on June 23, 2026. 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…
When was CVE-2026-54318 disclosed?
CVE-2026-54318 was first published in the National Vulnerability Database on June 23, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54318 actively exploited?
CVE-2026-54318 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54318?
CVE-2026-54318 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-54318?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54318, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-54318

Explore →

Is Your Infrastructure Affected by CVE-2026-54318?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs