CVE-2026-50083: Aqara hardcoded OAuth client credentials

Published Jun 12, 2026
·
Updated

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.

Affected Software

2 affected components
Aqara Aqara IAM/SSO Gateway
Aqara Iam\/sso Gateway=2026-04-20

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Replace the hardcoded OAuth client credential with unique, securely generated client credentials per deployment. Do not embed secrets in code or firmware; store credentials in a secure secret store or protected configuration and implement automated credential rotation.

    Aqara IAM/SSO Gateway (gw-builder.aqara.com) OAuth client credential = remove hardcoded credential; use unique per-deployment client credentials stored securely
  2. Compensating control

    If code/firmware updates cannot be applied immediately, restrict access to gw-builder.aqara.com and related management endpoints to trusted IP ranges and internal networks (firewall/ACL/WAF rules) to reduce remote exposure until the hardcoded credential is removed.

  3. Operational

    Revoke the hardcoded OAuth client credential and any OAuth tokens issued using it. Generate and deploy new client credentials, rotate them across affected systems, and invalidate any sessions that relied on the compromised credential.

Event History

Jun 12, 2026
CVE Published
via MITRE·03:00 PM
Data Sourced
via MITRE·03:00 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:16 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-50083?

CVE-2026-50083 has a critical severity rating of 9.1.

2

What vulnerabilities are related to CVE-2026-50083?

CVE-2026-50083 is related to CVE-2026-50082 and CVE-2026-50084.

3

How do I fix CVE-2026-50083?

To mitigate CVE-2026-50083, update to a version of the Aqara IAM/SSO Gateway that does not use hardcoded OAuth client credentials.

4

What type of vulnerability is CVE-2026-50083 categorized as?

CVE-2026-50083 is categorized as an instance of CWE-798: Use of Hard-coded Credentials.

5

What is the impact of CVE-2026-50083?

CVE-2026-50083 could result in unauthorized access due to exposed OAuth client credentials.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203