Skip to main content
VulnerabilityPublished

CVE-2026-33362: com.meari.sdk · Use of Hard-coded Cryptographic Key

Affects com.meari.sdkSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.6 High.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 3.1 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Mearicom.meari.sdkAffected
  • =firmID=8
Fixed in–

AI-suggested

Until a patch is released, consider minimizing exposure of affected SDK versions and avoid deploying affected versions in sensitive environments if possible.

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.

References

Community reviews

Loading reviews…