CVE-2026-50086
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Aqara IAM/SSO gateway (gw-builder.aqara.com) exposes bidirectional AES round-trups against the platform's signing key without authentication. This is an instance of "CWE-306: Missing Authentication for Critical Function" and "CWE-327: Use of a Broken or Risky Cryptographic Algorithm," and has an estimated CVSS of CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N (7.5 High).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Aqara IAM/SSO gateway (gw-builder.aqara.com) exposes bidirectional AES round-trips against the platform's signing key without any authentication required. This allows unauthenticated network attackers to potentially manipulate cryptographic operations, representing both CWE-306 (Missing Authentication for Critical Function) and CWE-327 (Use of a Broken or Risky Cryptographic Algorithm). The CVSS breakdown indicates network-exploitable access with high confidentiality impact.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2026-04-20CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the Aqara IAM/SSO GatewayDetermine if your environment includes the Aqara IAM/SSO Gateway service, typically accessible at the hostname gw-builder.aqara.com or configured as an authentication/single sign-on service in your networkAffected if The system is the Aqara IAM/SSO Gateway (gw-builder.aqara.com)
-
Check the installed versionRetrieve the firmware or software version of the Aqara IAM/SSO Gateway installation and compare it to the affected version 2026-04-20Affected if The installed version is exactly 2026-04-20
-
Verify network accessibility of gateway endpointsAttempt to access the gateway endpoints from an unauthenticated network perspective to confirm they are exposed externally or on untrusted network segmentsAffected if The gateway endpoints are network-accessible without requiring authentication
-
Confirm missing authentication on cryptographic endpointsSend test requests to the gateway's cryptographic endpoints (AES round-trip functionality) and verify that no authentication token or session is required to access these operationsAffected if The AES round-trip cryptographic endpoints respond without requiring any authentication credentials
You are affected if you are running the Aqara IAM/SSO Gateway version 2026-04-20 with its endpoints exposed to the network without authentication enabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement robust authentication on all gateway endpoints and replace the compromised signing key/algorithm with a standards-compliant cryptographic implementation. Consider network segmentation to limit exposure of the IAM gateway.
- Consultation8.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50086 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-50086 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data