CVE-2026-33357
Received Received - Intake
Meari Client WAN IP Exposure via Authorization Bypass

Publication date: 2026-05-11

Last updated on: 2026-05-11

Assigner: 44488dab-36db-4358-99f9-bc116477f914

Description
In Meari client applications embedding "com.meari.sdk" (including CloudEdge 5.5.0 build 220, Arenti 1.8.1 build 220, and related white-label <= 1.8.x), the integrated call path to openapi-euce.mearicloud.com can be abused to retrieve WAN IP data for arbitrary devices. The root cause is a server-side authorization failure in "GET /openapi/device/status".
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-11
Last Modified
2026-05-11
Generated
2026-05-11
AI Q&A
2026-05-11
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 3 associated CPEs
Vendor Product Version / Range
meari cloudedge 5.5.0
meari arenti 1.8.1
meari com.meari.sdk to 1.8.9 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2026-33357 is an Insecure Direct Object Reference (IDOR) vulnerability found in Meari client applications that embed the "com.meari.sdk" library, such as CloudEdge 5.5.0 build 220 and Arenti 1.8.1 build 220.

The vulnerability exists in the API endpoint "GET /openapi/device/status", which lacks proper authorization checks on the server side.

Because of this missing authorization, attackers can exploit the API to retrieve the WAN IP addresses of arbitrary devices without authentication.

This allows unauthorized access to sensitive network location data, enabling geolocation of consumer camera installations.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

CVE-2026-33357 allows unauthorized access to sensitive network location data, specifically WAN IP addresses of arbitrary devices, which can facilitate geolocation and profiling of consumer camera installations without authentication.

This unauthorized disclosure of sensitive device location information could potentially violate privacy regulations such as GDPR, which mandates protection of personal data and location information, and may also impact compliance with other data protection standards that require strict access controls and authorization mechanisms.

By enabling attackers to map physical locations of devices and potentially stalk or profile individuals, the vulnerability raises significant privacy and security concerns relevant to regulatory compliance.


How can this vulnerability impact me? :

This vulnerability can have significant privacy and security impacts.

  • Attackers can obtain WAN IP addresses of devices, which can be used to determine their physical locations.
  • It facilitates stalking, reconnaissance, and target profiling by enabling mass mapping of deployed cameras.
  • When combined with other vulnerabilities (like CVE-2026-33356), attackers can identify device identifiers and enrich that information with geolocation data.

How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by monitoring for unauthorized or suspicious API calls to the endpoint "GET /openapi/device/status" on the openapi-euce.mearicloud.com server.

Specifically, detection involves identifying requests that attempt to retrieve WAN IP data for arbitrary devices without proper authorization.

Since the vulnerability involves an insecure direct object reference (IDOR), network traffic analysis tools or API gateway logs can be used to detect unusual or mass queries to this endpoint.

Suggested commands or approaches include:

  • Using network packet capture tools like tcpdump or Wireshark to filter HTTP GET requests to openapi-euce.mearicloud.com/openapi/device/status.
  • Example tcpdump command: tcpdump -i <interface> -A 'tcp port 80 or tcp port 443' | grep '/openapi/device/status'
  • Reviewing API gateway or proxy logs for repeated or unauthorized access attempts to the vulnerable endpoint.
  • Searching MQTT traffic for device identifiers (in combination with CVE-2026-33356) to correlate with suspicious OpenAPI queries.

What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include restricting access to the vulnerable API endpoint "GET /openapi/device/status" to authorized users only.

Implement proper authorization checks on the server side to prevent unauthorized retrieval of WAN IP data.

If possible, update the Meari client applications and embedded SDKs to versions where this vulnerability is patched.

Monitor network and API traffic for suspicious activity targeting this endpoint and block or rate-limit abusive requests.

Consider disabling or limiting the use of the affected API until a fix is applied.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart