CVE-2026-50091
Awaiting Analysis Awaiting Analysis - Queue
Hard-coded Cryptographic Keys in Aqara Home Android

Publication date: 2026-06-12

Last updated on: 2026-06-12

Assigner: 44488dab-36db-4358-99f9-bc116477f914

Description
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 Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-12
Last Modified
2026-06-12
Generated
2026-06-12
AI Q&A
2026-06-12
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
aqara home_android to 6.0.0 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-321 The product uses a hard-coded, unchangeable cryptographic key.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Compliance Impact

The vulnerability involves hardcoded cryptographic keys that allow attackers to impersonate device pairing flows and decrypt encrypted content, which can lead to unauthorized access to sensitive data.

Such unauthorized access and potential data breaches can negatively impact compliance with data protection regulations like GDPR and HIPAA, which require strong protection of personal and sensitive information.

Because the vulnerability compromises confidentiality and integrity of data, affected organizations may face challenges in meeting the security requirements mandated by these standards.

Executive Summary

CVE-2026-50091 is a critical vulnerability in the Aqara Home Android SDK version 6.0.0 and its white-label clients that embed the same vulnerable library (liblumidevsdk.so). The issue arises from the use of hardcoded cryptographic keys, which are static and identical across all installations. This flaw falls under CWE-321: Use of Hard-coded Cryptographic Key.

Because these keys are hardcoded and shared, attackers can exploit them to forge camera authentication signatures, impersonate device pairing flows, and decrypt encrypted content by positioning themselves as privileged man-in-the-middle attackers.

Resolving this vulnerability requires coordinated firmware and app updates across the entire ecosystem.

Impact Analysis

This vulnerability can have severe impacts including unauthorized access and control over devices using the Aqara Home Android SDK. Attackers can forge authentication signatures to impersonate legitimate devices, intercept and decrypt sensitive encrypted data, and manipulate device pairing processes.

Such exploits can lead to privacy breaches, unauthorized surveillance, and compromise of the security and integrity of the affected smart home ecosystem.

Detection Guidance

This vulnerability involves the use of hardcoded cryptographic keys in the Aqara Home Android SDK and its white-label clients, specifically in the liblumidevsdk.so library. Detection would involve identifying the presence of this vulnerable library or the specific version of the Aqara Home Android app (version 6.0.0) on devices.

Since the keys are hardcoded and identical across installations, detection might include scanning for the vulnerable library file or monitoring network traffic for forged camera authentication signatures or unusual device pairing flows that could indicate exploitation attempts.

However, no specific detection commands or tools are provided in the available information.

Mitigation Strategies

Immediate mitigation requires coordinated firmware and app updates across the entire Aqara ecosystem, as the vulnerability stems from hardcoded cryptographic keys embedded in the SDK library.

Users and administrators should ensure that all devices and applications are updated to versions where the vulnerability has been addressed, noting that most issues were remediated by April 8, 2026, but some remained unfixed as of April 20, 2026.

Until updates are applied, monitoring for suspicious activity related to camera authentication or device pairing is advisable, but no direct workaround or patch is available without vendor coordination.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-50091. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart