CVE-2026-33356
Meari IoT Cloud MQTT Broker EMQX Subscribe Authorization Bypass
Publication date: 2026-05-11
Last updated on: 2026-05-11
Assigner: 44488dab-36db-4358-99f9-bc116477f914
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| meari | iot_cloud_mqtt_broker | From 4.0 (inc) to 5.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-639 | The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows any authenticated low-privilege user to access telemetry data and sensitive information from devices they do not own, breaking tenant isolation and exposing private data across unrelated customer accounts.
This unauthorized access to sensitive personal and device data could lead to violations of data protection regulations such as GDPR, which mandates strict controls on personal data access and processing.
Similarly, for regulations like HIPAA, if the exposed telemetry or device data includes protected health information, this vulnerability could result in non-compliance due to unauthorized disclosure.
Overall, the lack of per-device subscribe authorization undermines confidentiality and data access controls required by common standards and regulations.
Can you explain this vulnerability to me?
CVE-2026-33356 is a security vulnerability in the Meari IoT Cloud MQTT Broker running on EMQX 4.x. It allows any authenticated low-privilege user to subscribe to global wildcard topics and receive telemetry data from devices they do not own.
While the broker enforces restrictions on publishing messages, it does not enforce equivalent authorization controls on subscribing to topics at the per-device level. This means users can bypass tenant isolation for read access and access telemetry, alerts, and camera data from unrelated customer devices.
The vulnerability is classified as CWE-639 (Authorization Bypass Through User-Controlled Key) and has a high CVSS score of 7.7.
How can this vulnerability impact me? :
This vulnerability can have severe impacts by exposing sensitive telemetry and private data from devices you do not own.
- Unauthorized users can receive real-time motion alerts, device-binding events, and other sensitive information from all devices on the platform.
- It breaks tenant isolation, allowing attackers to surveil households and collect sensitive data without permission.
- The exposure includes platform-wide device events such as alert metadata and camera artifact links.
- Attackers with normal cloud accounts can exploit this vulnerability to conduct surveillance and potentially launch follow-on attacks.
- The vulnerability affects over 1.1 million registered devices globally, making the impact widespread.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring MQTT broker subscriptions for unauthorized access to global wildcard topics such as "meari/#". An authenticated low-privilege user subscribing to such wildcard topics and receiving telemetry data from devices they do not own indicates the presence of the vulnerability.
Commands to detect this might include using MQTT client tools to attempt subscribing to global wildcard topics with a low-privilege account and observing if telemetry data from unrelated devices is received.
- Use an MQTT client (e.g., mosquitto_sub) to subscribe to the wildcard topic: mosquitto_sub -h <broker_address> -t 'meari/#' -u <low_privilege_user> -P <password>
- Monitor network traffic for MQTT SUBSCRIBE packets to global wildcard topics from low-privilege accounts.
- Check broker logs for subscriptions to wildcard topics by users who should not have access to those devices.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting or disabling subscriptions to global wildcard topics for low-privilege users and implementing per-device subscribe authorization controls in the MQTT broker configuration.
Since the broker enforces publish restrictions but not subscribe restrictions, administrators should apply access control lists (ACLs) or equivalent mechanisms to enforce subscribe permissions at the per-device level.
Additionally, monitoring and auditing subscriptions to sensitive topics can help detect and prevent unauthorized data access.