CVE-2026-59717

MEDIUMPre-NVD 4.34.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (31st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-54646 (ENISA EUVD)Source: ENISA EUVD

4.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 4.3Exploit: No code on recordExposed services: Not assessed

The CVE record names the fixed release — apply it.

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.

CVSS v3
4.3
EG Score
4.3MEDIUMmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity43% × 45%
Impact severity (EG Severity): CVSS 4.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
31st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (4.3): severity, escalated by confirmed exploitation. This CVE's 4.3 is its impact severity (EG Severity), not escalated.

EG Severity
4.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 7, 2026

Last Modified

October 24, 2026

Advisory Details (3)

Auto-updated Aug 7, 2026
Fix named in the CVE record. Sources: github, github_pr, github_commit.
GitHub commit

commit 26154d923c38 (home-assistant/android)

Fix landed in home-assistant/android commit 26154d923c38 — awaiting tagged release

https://github.com/home-assistant/android/commit/26154d923c3813cd4650e124900780f4f796d094
GitHub pull request

Add dedicated screen for invitation flow instead of WelcomeScreen

Fix merged in home-assistant/android PR #6955 on 2026-06-02 — awaiting tagged release

https://github.com/home-assistant/android/pull/6955
GitHub advisoryMentions a patch (unverified)

Home Assistant Companion (Android) `homeassistant://invite` Deep Link Credential Phishing · Advisory · home-assistant/core · GitHub

https://github.com/home-assistant/core/security/advisories/GHSA-68f4-97mf-f68w

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 41× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 138 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 38 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  3. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  4. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  5. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  6. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  7. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  8. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  9. 2026-10-25 14:16 UTCEG score recompute
  10. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  11. 2026-10-23 20:31 UTCEG score recompute
  12. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  13. 2026-10-22 20:56 UTCEG score recompute
  14. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  15. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  16. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  17. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  18. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  19. 2026-10-18 03:27 UTCEG score recompute
  20. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  21. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  22. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  23. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  24. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  25. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 29th percentile
Show 75 more
  1. 2026-10-12 15:52 UTCEG score recompute
  2. 2026-10-11 19:36 UTCEG score recompute
  3. 2026-10-11 16:51 UTCEG score recompute
  4. 2026-10-11 14:13 UTCEG score recompute
  5. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  6. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  7. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  8. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  9. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  10. 2026-10-06 23:16 UTCEG score recompute
  11. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  12. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  13. 2026-10-05 08:11 UTCEG score recompute
  14. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  15. 2026-10-04 05:42 UTCEG score recompute
  16. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  17. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  18. 2026-10-02 09:31 UTCEG score recompute
  19. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  20. 2026-09-30 22:54 UTCEG score recompute
  21. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  22. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  23. 2026-09-29 05:42 UTCEG score recompute
  24. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  25. 2026-09-27 17:07 UTCEG score recompute
  26. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  27. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  28. 2026-09-25 05:12 UTCEG score recompute
  29. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  30. 2026-09-24 06:58 UTCEG score recompute
  31. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  32. 2026-09-23 08:45 UTCEG score recompute
  33. 2026-09-22 10:31 UTCEG score recompute
  34. 2026-09-21 12:01 UTCEG score recompute
  35. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  36. 2026-09-20 11:07 UTCEG score recompute
  37. 2026-09-19 12:53 UTCEG score recompute
  38. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  39. 2026-09-18 13:27 UTCEG score recompute
  40. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  41. 2026-09-17 15:10 UTCEG score recompute
  42. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  43. 2026-09-16 12:28 UTCEG score recompute
  44. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  45. 2026-09-15 14:14 UTCEG score recompute
  46. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  47. 2026-09-14 14:03 UTCEG score recompute
  48. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  49. 2026-09-12 17:29 UTCEG score recompute
  50. 2026-09-11 19:15 UTCEG score recompute
  51. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  52. 2026-09-10 20:52 UTCEG score recompute
  53. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  54. 2026-09-09 05:59 UTCEG score recompute
  55. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  56. 2026-09-07 17:42 UTCEG score recompute
  57. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  58. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  59. 2026-09-06 05:28 UTCEG score recompute
  60. 2026-09-05 07:13 UTCEG score recompute
  61. 2026-09-04 08:59 UTCEG score recompute
  62. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  63. 2026-09-03 05:58 UTCEG score recompute
  64. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  65. 2026-09-02 06:45 UTCEG score recompute
  66. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  67. 2026-09-01 07:10 UTCEG score recompute
  68. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  69. 2026-08-31 06:54 UTCEG score recompute
  70. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  71. 2026-08-30 08:40 UTCEG score recompute
  72. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  73. 2026-08-29 10:21 UTCEG score recompute
  74. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  75. 2026-08-28 11:52 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-59717?
CVE-2026-59717 is a medium-severity vulnerability; its CVE record was published on August 7, 2026. 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…
When was the CVE record for CVE-2026-59717 published?
The CVE record for CVE-2026-59717 was published on August 7, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-59717 actively exploited?
CVE-2026-59717 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-59717?
CVE-2026-59717 has a CVSS base score of 4.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-59717?
The CVE record for CVE-2026-59717 names the fix: "This issue is fixed in version 2026.6.1."

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-59717?

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