CVE-2026-50091

CRITICALNVD 7.49.1
EchelonGraph scoreMEDIUM confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-12. NVD baseline CVSS 7.4; sources differ by 1.7.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated
9.1EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (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: 7.4Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (runZero, Inc.) lists Aqara com.lumiunited.aqarahome versions 6.0.0 up to but not including 0 as affected. No release containing a fix is confirmed on record.

Aqara Home Android (com.lumiunited.aqarahome) 6.0.0 (and white-label clients embedding the same liblumidevsdk.so) uses hard-coded cryptographic keys, which is an instance of "CWE-321: Use of Hard-coded Cryptographic Key" and has an estimated CVSS of CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N (9.1 Critical).

CVSS v3
7.4
EG Score
9.1CRITICALmedium confidence
EG Risk
72
EG Risk 72/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
The EG Score, 9.1 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (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

June 12, 2026

Last Modified

July 9, 2026

Advisory Details (2)

Auto-updated Jun 12, 2026
No fix on record yet.
Web page

GitHub - xn0tsa/theres-no-place-like-home: Ten CVEs against the Aqara/Lumi IoT cloud platform — public disclosure 2026-06-11 · GitHub

https://github.com/xn0tsa/theres-no-place-like-home
Web page

Aqara Home Android SDK hardcoded keys

https://www.runzero.com/advisories/aqara-hardcoded-sdk-keys-cve-2026-50091

Vendor Advisories for CVE-2026-50091(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 32× 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 473 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 373 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-50091?
CVE-2026-50091 is a critical-severity vulnerability; its CVE record was published on June 12, 2026. Aqara Home Android (com.lumiunited.aqarahome) 6.0.0 (and white-label clients embedding the same liblumidevsdk.so) uses hard-coded cryptographic keys, which is an instance of "CWE-321: Use of Hard-coded Cryptographic Key" and has an estimated CVSS of CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N (9.1…
When was CVE-2026-50091 made public?
CVE-2026-50091 was made public on June 12, 2026: that is the date its CVE record's CNA, runZero, Inc., gives for when the vulnerability was made public. The CVE record itself was published on June 12, 2026. EchelonGraph's copy of the record carries a last-modified date of July 9, 2026; the record at its source may have been updated since.
Is CVE-2026-50091 actively exploited?
CVE-2026-50091 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-50091?
CVE-2026-50091 has a CVSS v3 base score of 7.4 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.1 (CRITICAL).
How do I remediate CVE-2026-50091?
No fix for CVE-2026-50091 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (runZero, Inc.) lists Aqara com.lumiunited.aqarahome versions 6.0.0 up to but not including 0 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-50091 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-50091?

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

Book a Demo →Browse All CVEs