{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59717 exists.","fix":"No fix has been published for CVE-2026-59717 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-59717 is a medium-severity vulnerability in home-assistant core, published on 7 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-59717 and fix it if it is affected.\n\nWhat it is: CVE-2026-59717 is a medium-severity vulnerability in home-assistant core, published on 7 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59717 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-59717/ (Markdown: https://insights.sbomify.com/CVE-2026-59717/index.md)","id":"CVE-2026-59717","markdown":"https://insights.sbomify.com/CVE-2026-59717/index.md","name":"CVE-2026-59717","record":{"aliases":["GHSA-68f4-97mf-f68w"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Home Assistant Android app","requires_auth":"none","summary":"Attackers can phish credentials by redirecting users to malicious login pages via deep links in the Home Assistant Android app.","user_interaction":"required","vuln_class":"open_redirect"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-939","name":"Improper Authorization in Handler for Custom URL Scheme"},{"id":"CWE-601","name":"URL Redirection to Untrusted Site"}],"description":"Home Assistant is open source home automation software focused on local control and privacy. Prior to 2026.6.1, the Android Companion app is vulnerable to an open redirect. The app passes the URL fragment from a homeassistant://invite deep link into the onboarding flow without ever displaying the destination hostname. Because no screen in the invitation or onboarding flow shows the parsed server URL before onboarding commits to it, a victim has no way to distinguish a legitimate invite from a malicious one. An attacker can craft an invite so that a single tap on the legitimate-looking \"Connect to my Home Assistant server\" button opens their /auth/authorize endpoint in the URL-less onboarding WebView, presenting a look-alike login page that captures the victim's credentials. Since invitations are intended to onboard brand-new users, targets are especially unlikely to notice the substitution. This issue is fixed in version 2026.6.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 Companion: `homeassistant://invite` Deep Link Credential Phishing","id":"CVE-2026-59717","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"open_redirect","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Hoppscotch: Insecure Default Configuration Allows Public Exposure of Private Collection Data via Mock Server","id":"CVE-2026-59720"},"packages":[],"prev":{"headline":"Open WebUI: Unauthenticated WebSocket Access to Collaborative Document Handlers (ydoc:awareness:update, ydoc:document:leave)","id":"CVE-2026-59715"},"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-07","vendors":["home-assistant"]},"summary":"Attackers can phish credentials by redirecting users to malicious login pages via deep links in the Home Assistant Android app.","url":"https://insights.sbomify.com/CVE-2026-59717/"}