# CVE-2026-50085: Aqara Board IoT insecure debug API

> Attackers can send arbitrary MQTT commands to the Aqara Board service without authentication, potentially leading to remote device takeover.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jun 2026
- **Updated:** 12 Jun 2026
- **Also known as:** GHSA-xrr5-fhq2-5w4h

## What is CVE-2026-50085?

CVE-2026-50085 is a high-severity missing authorization vulnerability in Aqara Board service, published on 12 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Aqara Board service (op-test.aqara.com) accepts arbitrary MQTT command payloads, and forwards them to the platfom's HiveMQ broker without authentication. This is an instance of "CWE-306: Missing Authentication for Critical Function" and has an estimated CVSS ofCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L (8.6 High). When combined with CVE-2026-50082, CVE-50083, and CVE-50084, this can lead to a fully unauthenticated, remote takeover of affected devices.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-50085?

It affects 1 product.


Products: Aqara Board Service.

## How do I fix CVE-2026-50085?

No fix has been published for CVE-2026-50085 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-50085 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-50085 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-50085 and fix it if it is affected.

What it is: CVE-2026-50085 is a high-severity missing authorization vulnerability in Aqara Board service, published on 12 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-50085 exists.

Affected product: Aqara Board service. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-50085/ (Markdown: https://insights.sbomify.com/CVE-2026-50085/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-50085
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-50085
- OSV: https://osv.dev/vulnerability/CVE-2026-50085

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-50085/
Summaries are generated and may contain mistakes; the official description above is the record.