CVE-2026-50088
Permissive CORS in Aqara dev portals allows cross-origin data exposure.
Is CVE-2026-50088 being exploited?
Not confirmed. CVE-2026-50088 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.21% probability of exploitation in the next 30 days.
How severe is CVE-2026-50088?
CVE-2026-50088 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-50088?
Yes. A fix has been recorded for CVE-2026-50088. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-50088 affect?
CVE-2026-50088 affects Aqara Developer Portal, developer.aqara.com, developer-test.aqara.com, aiot-test.aqara.com. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-50088?
Enforce strict CORS; audit dev portals; apply patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Data disclosure via cross-origin requests from dev/test portals; requires user interaction to exploit.
Patch when possible
- affected>= 2026-04-20 and < 0
- affected>= 2026-04-20 and < 0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.