dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-33357

HIGH · 7.5 CVSS v3.1 Published 2026-05-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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".

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A server-side authorization failure in the GET /openapi/device/status endpoint allows attackers to retrieve WAN IP addresses for arbitrary devices by manipulating device identifiers in requests to openapi-euce.mearicloud.com. The vulnerability stems from missing or insufficient access control checks that should verify the requesting user owns or has permission to access the target device.

MitigationImplement proper server-side authorization checks to ensure users can only access device status information for devices they own or are authorized to view. Validate session tokens and device ownership before returning any device data.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify MeariCloud integration
    Review your application codebase and configuration files for references to 'openapi-euce.mearicloud.com' or 'mearicloud' API endpoints. Check API client configurations, environment variables, and service definitions.
    Affected if Your system integrates with or calls the openapi-euce.mearicloud.com API service.
  2. Locate the /openapi/device/status endpoint
    Search your API proxy configurations, route definitions, and web server logs for access to '/openapi/device/status' path. Use grep or log analysis tools to find requests matching this endpoint pattern.
    Affected if The /openapi/device/status endpoint is exposed in your environment.
  3. Verify authorization is enforced on the endpoint
    Examine the authentication and authorization logic for the device status endpoint. Review access control middleware, session validation code, and ownership verification routines. Test by attempting to access device status for a device you do not own using valid but unauthorized credentials.
    Affected if The endpoint allows retrieval of device WAN IP addresses without verifying that the requesting user owns or is authorized to access the target device.
  4. Check for device identifier manipulation vulnerability
    Perform a controlled test: send requests to /openapi/device/status with different device identifiers (not belonging to your authenticated session). Compare the responses to determine if arbitrary device data is returned.
    Affected if Requesting device status with a manipulated device identifier returns WAN IP information for devices outside your authorization scope.

Your environment is affected if it integrates with the MeariCloud openapi-euce.mearicloud.com service and the /openapi/device/status endpoint returns WAN IP addresses for devices without proper ownership verification.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper server-side authorization checks to ensure users can only access device status information for devices they own or are authorized to view. Validate session tokens and device ownership before returning any device data.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33357 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-33357 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data