PatchSiren cyber security CVE debrief
CVE-2026-66060 home-assistant CVE debrief
Home Assistant, an open-source home automation software, had a vulnerability prior to version 2026.5.3. The Companion app could be exploited by any untrusted app on the device to execute automations silently without user interaction, by forwarding arbitrary tag links. This issue is fixed in version 2026.8.1. The vulnerability allows untrusted local apps to execute Home Assistant automations silently, requiring defenders to upgrade to version 2026.8.1 or later and monitor for suspicious activity.
- Vendor
- home-assistant
- Product
- core
- CVSS
- HIGH 7.1
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-07
- Original CVE updated
- 2026-09-09
- Advisory published
- 2026-08-07
- Advisory updated
- 2026-09-09
Who should care
Defenders responsible for Home Assistant deployments should assess exposure and prioritize upgrading to version 2026.8.1 or later to prevent silent automation execution by untrusted local callers.
Why it matters
CVE-2026-66060 allows untrusted local apps to execute Home Assistant automations silently, requiring defenders to upgrade to version 2026.8.1 or later and monitor for suspicious activity.
- Untrusted local apps can execute automations without user interaction
- Silent automation execution can lead to unintended actions
- Defenders must verify and upgrade to version 2026.8.1 or later
- Local access is required for exploitation
Technical summary
The Companion app in Home Assistant prior to 2026.5.3 treats tag links delivered through an OS-level routing mechanism as if they were physically scanned, without validating the calling app or prompting the user. This allows any untrusted app on the device to forward an arbitrary tag to Home Assistant, causing it to execute the associated automation silently. The issue is fixed in version 2026.8.1, and defenders should prioritize upgrading to this version or later to prevent silent automation execution by untrusted local callers.
Defensive priority
Defenders should prioritize upgrading to version 2026.8.1 or later to prevent silent automation execution by untrusted local callers.
Recommended defensive actions
- Upgrade to Home Assistant version 2026.8.1 or later
- Restrict access to the Companion app to trusted sources only
- Monitor for suspicious automation executions
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE record and NVD entry provide details on the vulnerability, its impact, and the fix. However, the scope of affected versions and potential exploitation remains limited to local untrusted apps. The vulnerability was publicly disclosed on 2026-08-07 and has not been modified since then. The Home Assistant community and developers have confirmed the issue and provided guidance on mitigation and remediation.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-66060 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-66060
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-66060 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-66060
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/home-assistant/android/commit/968b49c58e4eba4d06371a3f6e73198ec6c8d4a7
-
Source reference
Unverified legacy reference
URL: https://github.com/home-assistant/core/security/advisories/GHSA-2xqv-hwrf-983f
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.