Vulnerability in Home Assistant (CVE-2026-54318)
Summary
Vulnerability in Home Assistant (CVE-2026-54318). Data can be tampered with by attackers. Mitigation: upgrade to 2026.5.3 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54318 has been found in Home Assistant.
Data can be tampered with by attackers. CVSS score: 7.1/10.
What to do: upgrade Home Assistant to 2026.5.3 or later.
If unsure, ask your IT team or search "Home Assistant CVE-2026-54318" on the vendor's site.
CVE-2026-54318 (Home Assistant) — CWE-926 / CVSS v3 7.1
Attack vector: local / unauthenticated / no user interaction
Patched: 2026.5.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-926) exists in Home Assistant.
Check the vendor advisory for the affected versions of Home Assistant.
Severity: High (CVSS 7.1/10). Data can be tampered with by attackers.
Update to 2026.5.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Home Assistant を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade Home Assistant to 2026.5.3ステージング環境で 2026.5.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com