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

> Attackers can extract hardcoded cryptographic keys from the Meari IoT SDK to bypass security controls and access sensitive data in associated mobile applications.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 May 2026
- **Updated:** 11 May 2026
- **Also known as:** GHSA-w7mj-frmj-5g6g

## What is CVE-2026-33362?

CVE-2026-33362 is a high-severity vulnerability in com.meari.sdk, published on 11 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

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

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

## Which versions are affected by CVE-2026-33362?


## How do I fix CVE-2026-33362?

No fix has been published for CVE-2026-33362 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-33362 being exploited?

There is no known exploitation of CVE-2026-33362 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33362 and fix it if it is affected.

What it is: CVE-2026-33362 is a high-severity vulnerability in com.meari.sdk, published on 11 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-33362 in the wild and no public exploit code.

Affected product: com.meari.sdk. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33362/ (Markdown: https://insights.sbomify.com/CVE-2026-33362/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33362
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33362
- OSV: https://osv.dev/vulnerability/CVE-2026-33362

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33362/
Summaries are generated and may contain mistakes; the official description above is the record.