# CVE-2026-50084: Aqara Cloud Production API Missing Authorization in User-Scope Endpoints

Source: https://junglewise.ai/threats/cve-2026-50084-aqara-cloud-production-api-missing-authorization-in-user-scope  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-06-12. Updated: 2026-06-12  
License: CC BY 4.0 with a link back

CVE-2026-50084 · Severity: critical · CVSS 9.6 · Published 2026-06-12

The Aqara Cloud Production API, which manages smart home devices like locks and cameras, contains a flaw that allows any registered developer to access other users' accounts. By using a valid developer token, an attacker could remotely control smart devices or view private data belonging to any customer on the platform. When combined with other vulnerabilities, this could allow an unauthorized person to take full control of a home's smart security system without needing a password.

Vendors: [Aqara](https://junglewise.ai/threats/vendors/aqara).

## Quick answers

**Is CVE-2026-50084 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-50084 being exploited in the wild.

**How severe is CVE-2026-50084?** Critical severity, with a CVSS score of 9.6, published 12 June 2026.

**Which products and versions are affected?** Aqara Cloud Production API v3.0.

**Is there a fix for CVE-2026-50084?** A patch was published on 2026-04-08: Vulnerabilities remediated by vendor Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-50084 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2026-50084?** Check whether you run Aqara Cloud Production API at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability is a 'Missing Authorization' (CWE-862) flaw within the Aqara Cloud Production API. While the API uses an MD5-based signing primitive for request authentication, it fails to verify if the authenticated developer (Appid) has permission to access the specific user-scope endpoints or resources requested. An attacker with a valid developer token—which can be obtained for free—can perform read/write operations against arbitrary user accounts. This issue serves as a critical step in an exploit chain that enables unauthenticated remote takeover of IoT devices including smart locks and cameras. The vendor reportedly remediated the issue in April 2026.

## Affected products

- Aqara Cloud Production API v3.0

## Timeline

- 2026-03-13: disclosed: Initial researcher outreach to vendor
- 2026-04-08: patched: Vulnerabilities remediated by vendor
- 2026-04-20: other: Vendor acknowledged researcher reporting and confirmed fix
- 2026-06-12: advisory: Public disclosure

## References

- [https://github.com/xn0tsa/theres-no-place-like-home](https://github.com/xn0tsa/theres-no-place-like-home)
- [https://www.runzero.com/advisories/aqara-api-access-cve-2026-50084](https://www.runzero.com/advisories/aqara-api-access-cve-2026-50084)