{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-66060 exists.","fix":"No fix has been published for CVE-2026-66060 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-66060 is a high-severity missing authorization vulnerability in home-assistant core, published on 7 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-66060 and fix it if it is affected.\n\nWhat it is: CVE-2026-66060 is a high-severity missing authorization vulnerability in home-assistant core, published on 7 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-66060 exists.\n\nAffected product: home-assistant core. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-66060/ (Markdown: https://insights.sbomify.com/CVE-2026-66060/index.md)","id":"CVE-2026-66060","markdown":"https://insights.sbomify.com/CVE-2026-66060/index.md","name":"CVE-2026-66060","record":{"aliases":["GHSA-2xqv-hwrf-983f"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["privilege_escalation","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Home Assistant Companion app","requires_auth":"none","summary":"Untrusted apps can silently trigger Home Assistant automations by spoofing NFC/QR scans, bypassing user confirmation and authorization checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Home Assistant is open source home automation software focused on local control and privacy.  Prior to 2026.5.3,  the Companion app treats tag links (NFC or QR) delivered through an OS-level routing mechanism as if they were physically scanned, without validating the calling app or prompting the user. As a result, any untrusted app on the device can forward an arbitrary tag to Home Assistant, causing it to execute the associated automation as though a legitimate user had scanned an authorized tag. This allows silent, unattended automation execution by untrusted local callers. This issue is fixed in version 2026.8.1.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Home Assistant: Unconfirmed NFC/QR tag scans allow silent automation execution by untrusted callers","id":"CVE-2026-66060","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Home Assistant: iOS Companion app forwards NFC/QR tag scans without confirmation, enabling silent automation execution","id":"CVE-2026-66061"},"packages":[],"prev":{"headline":"Frappe: Field-level permission bypass via Document Follow","id":"CVE-2026-66059"},"products":["core"],"published":"2026-08-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-13","vendors":["home-assistant"]},"summary":"Untrusted apps can silently trigger Home Assistant automations by spoofing NFC/QR scans, bypassing user confirmation and authorization checks.","url":"https://insights.sbomify.com/CVE-2026-66060/"}