Loading vulnerability…
CVE-2026-50084 is a missing-authorization flaw in the Aqara Cloud Production API at open-cn.aqara.com/v3.0/open/api. According to the provided content, the API authenticates requests using a developer Appid/token and an MD5-based request-signature scheme, but fails to enforce proper account-level authorization on user-scope endpoints. As a result, any valid developer token/Appid is accepted as sufficient authorization to perform API calls against arbitrary Aqara accounts rather than being restricted to the account it should be associated with. This is described as a cross-account access control failure affecting the production API.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.