CVE-2026-50090: Aqara OAuth redirect_uri validation bypass

Published Jun 12, 2026
·
Updated

The Aqara Cloud OAuth Authorization Endpoint (open-cn.aqara.com/oauth/authorize) is vulnerable to a redirect bypass due to lax controls on domain matching, which is an instance of "CWE-1289: Improper Validation of Unsafe Equivalence in Input" and has an estimated CVSS of CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N (9.3 Critical).

Affected Software

2 affected components
Aqara Aqara Cloud OAuth Authorization Endpoint (open-cn.aqara.com/oauth/authorize)
Aqara Cloud OAuth Authorization Endpoint=2026-04-20

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Enforce strict (exact) comparison of the redirect_uri in incoming authorization requests against a whitelist of pre-registered redirect URIs. Compare scheme, host, port and path exactly; disallow wildcard, partial, or equivalence-based domain matches that enable redirect bypass.

    Aqara Cloud OAuth Authorization Endpoint (open-cn.aqara.com/oauth/authorize) redirect_uri validation / domain matching = strict exact match (no wildcards or equivalence-based matching)
  2. Configuration

    Require all clients to pre-register exact redirect_uri values and reject authorization requests where the redirect_uri does not exactly match one of the registered values.

    OAuth client registration accept_only_registered_redirect_uris = true
  3. Compensating control

    If immediate code changes are not possible, deploy WAF or reverse-proxy rules to block authorization requests where the redirect_uri parameter points to untrusted or unregistered domains or that use patterns indicative of domain-matching bypass (e.g., appended domains, encoded separators). Log and alert on blocked attempts.

  4. Operational

    Audit all existing OAuth client registrations and authorization logs for uses of lax or ambiguous redirect URIs; update or remove registrations that rely on permissive domain matching and remediate any clients that may be affected.

Event History

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

Frequently Asked Questions

1

What is the severity of CVE-2026-50090?

The severity of CVE-2026-50090 is rated as critical with a score of 9.3.

2

How do I fix CVE-2026-50090?

To mitigate CVE-2026-50090, ensure strict validation checks on redirect_uri parameters in the OAuth Authorization process.

3

What kind of vulnerability is CVE-2026-50090?

CVE-2026-50090 is an instance of improper validation of unsafe equivalence in input, specifically related to redirect URI validation.

4

What systems are affected by CVE-2026-50090?

CVE-2026-50090 affects the Aqara Cloud OAuth Authorization Endpoint located at open-cn.aqara.com/oauth/authorize.

5

What are the potential impacts of CVE-2026-50090?

The potential impacts of CVE-2026-50090 include unauthorized access and redirection to malicious sites due to lax domain matching.

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