Aqara hardcoded OAuth client credentials
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-798.
Summary
The Aqara IAM/SSO Gateway (gw-builder.aqara.com) used a hardcoded OAuth client credential, which is an instance of "CWE-798: Use of Hard-coded Credentials." This issue 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). When combined with CVE-2026-50082, CVE-50084, and CVE-50085, this can lead to a fully unauthenticated, remote takeover of affected devices.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- Yes
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
- Fix · CNA Aquara IAM/SSO Gateway (Aqara) Fixed in 0
Timeline
- 2026-10-02 Threatist record created from CVE-2026-50083
- 2026-10-03 Alias added: GHSA-h5g5-hrhr-3ph4
References
More Aqara Iam/sso Gateway vulnerabilities
- TI-2026-36879 Aqara unauthenticated AES oracle CVSS 3.1CRITICAL 10.0
- TI-2026-36882 Aqara IAM/SSO Gateway open redirect CVSS 3.1MEDIUM 6.1
- TI-2026-36880 Aqara IAM/SSO Gateway cross-origin resource sharing CVSS 3.1HIGH 8.2
Sources
- CVE-2026-50083 · CVE Program
- CVE-2026-50083 · NVD
- FIRST EPSS
- GHSA-h5g5-hrhr-3ph4 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences