Skip to content
IoT

CVE-2026-50091

9.1
Critical
EPSS 0.29%Patch availableJun 13, 2026

Aqara Home Android app uses hard-coded crypto keys (CWE-321), CVSS 9.1.

common questions

Is CVE-2026-50091 being exploited?

Not confirmed. CVE-2026-50091 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.29% probability of exploitation in the next 30 days.

How severe is CVE-2026-50091?

CVE-2026-50091 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-50091?

Yes. A fix has been recorded for CVE-2026-50091. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-50091 affect?

CVE-2026-50091 affects Aqara Home Android app (com.lumiunited.aqarahome) 6.0.0, white-label apps embedding liblumidevsdk.so. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-50091?

Update to patched version when available; remove hard-coded keys and rotate crypto material.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Aqara Home Android app (com.lumiunited.aqarahome) 6.0.0white-label apps embedding liblumidevsdk.so
impact

Remote attacker could decrypt and tamper data due to hard-coded crypto keys; confidentiality and integrity impact (high); availability unaffected.

action required

Patch when possible

affected versions
Aqara com.lumiunited.aqarahome
  • affected>= 6.0.0 and < 0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free