Loading vulnerability…
CVE-2026-33362 affects Meari IoT SDK builds embedded in CloudEdge 5.5.0 (build 220), Arenti 1.8.1 (build 220), and observed white-label Android apps in the 1.8.x line. The issue consists of multiple security-critical secrets being hardcoded into applications and shared across the ecosystem, including API signing material, a password-transport DES key, an OpenAPI key, and peer-to-peer service credentials. The disclosed reporting indicates these values are static and reused across Meari-powered applications and devices rather than being uniquely provisioned per device, per tenant, or per deployment. Because the secrets are embedded and shared, compromise of one app build or reverse engineering of one client can expose credentials usable more broadly across the platform. The disclosure further notes that these secrets are effectively permanent in deployed devices because rotation would require reflashing affected hardware in the field.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.