CriticalPublic exploit

Hardcoded OAuth Client Credentials in Aqara IAM/SSO Gateway

IdentifiersCVE-2026-50083CWE-798· Use of Hard-coded Credentials

CVE-2026-50083 affects the Aqara IAM/SSO Gateway at gw-builder.aqara.com. The issue is the use of hardcoded OAuth client credentials in the platform, classified as CWE-798. The provided content states that two OAuth client credential pairs were hardcoded and accepted by the gateway, including test1:123456 and test:123456. These credentials could be used against the gateway’s OAuth flow to obtain access tokens with scope=all, including very long-lived tokens reportedly extending as far as September 2083. The vulnerability therefore exposes embedded authentication material that should not be present in production-accessible systems and allows unauthorized parties to mint broadly scoped OAuth tokens without possessing legitimately issued client secrets. The content further states that this weakness is one component of a larger attack chain involving CVE-2026-50082, CVE-2026-50084, and CVE-2026-50085.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a remote unauthenticated attacker to abuse hardcoded OAuth client credentials to obtain highly privileged OAuth tokens from gw-builder.aqara.com. Based on the supplied CVSS vector and supporting content, the primary impact is high confidentiality and integrity compromise, because the attacker can acquire scope=all tokens and use them in downstream Aqara cloud workflows. The content specifically states that, when chained with CVE-2026-50082, CVE-2026-50084, and CVE-2026-50085, this issue can contribute to a fully unauthenticated remote takeover of affected Aqara devices. No direct availability impact is specifically claimed for this CVE in isolation.

Mitigation

If you can’t patch tonight, do this now.

Until full remediation is confirmed, defenders should disable or block the affected OAuth clients at the gateway, revoke outstanding tokens associated with the hardcoded credentials, and monitor authentication logs for use of the known credential pairs and anomalous token issuance from gw-builder.aqara.com. Additional temporary controls include IP-based restrictions on token endpoints where feasible, tighter downstream authorization checks on APIs consuming these tokens, and detection for tokens with unusually broad scope or excessive lifetime. Because the content states this CVE is especially dangerous when chained with CVE-2026-50082, CVE-2026-50084, and CVE-2026-50085, mitigation should also prioritize blocking those adjacent attack paths.

Remediation

Patch, then assume compromise.

Remove all hardcoded OAuth client credentials from the Aqara IAM/SSO Gateway and any associated code, configuration, mobile applications, SDKs, build artifacts, and repositories. Revoke and rotate all exposed client IDs and client secrets, invalidate any tokens issued via those credentials, and audit for long-lived tokens already minted using the embedded secrets. Restrict token issuance so that only explicitly authorized clients can obtain tokens, reduce token scope from broad values such as scope=all to least privilege, and enforce short token lifetimes with robust client authentication controls. Because the content indicates that the exposed credentials were accepted by a production-accessible gateway, remediation should also include a review of environment separation and secret-management practices to ensure test or legacy credentials cannot be used against production services.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

AqaraIam Sso Gatewayapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

5 SOURCESView more in app

cvefeed high severityNews

Jun 12, 2026

CVE-2026-50083 - Aqara hardcoded OAuth client credentials

A critical hardcoded OAuth client credential vulnerability in the Aqara IAM/SSO Gateway (gw-builder.aqara.com) that can contribute to fully unauthenticated remote takeover of affected devices when chained with other vulnerabilities.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity4

Community discussion across Reddit, Mastodon, and other social sources.

EXTERNAL REFERENCES

MITRE CVE

cve.org · CVE-2026-50083

NVD

nvd.nist.gov/vuln/detail/CVE-2026-50083

MITRE CWE · CWE-798

Use of Hard-coded Credentials

Third Party Advisory

github.com/xn0tsa/theres-no-place-like-home

Third Party Advisory

runzero.com/advisories/aqara-hardcoded-oauth-cve-2026-50083

Hardcoded OAuth Client Credentials in Aqara IAM/SSO Gateway

IdentifiersCVE-2026-50083CWE-798· Use of Hard-coded Credentials