Skip to main content
VulnerabilityPublished

CVE-2026-33356: Meari IoT Cloud MQTT Broker EMQX · Insecure Direct Object Reference

Affects Meari IoT Cloud MQTT Broker EMQXSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.7 High : upgrade to 5.0.0 soon.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
7.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.0.0
CVSS:3.1/AV:N/AC:L/PR:L/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 16 Nov 2026.

What to do

Upgrade xn0tsa/nobody-puts-baby-in-a-corner to 5.0.0.

Affected software

ProductAffectedFixed in
MeariIoT Cloud MQTT Broker EMQXAffected
  • =>=4.0.0 <5.0.0
Fixed in–
GitHubxn0tsa/nobody-puts-baby-in-a-cornerpkg:github/xn0tsa/nobody-puts-baby-in-a-cornerOther threatsAffected
  • <5.0.0 >=4.0.0
Fixed in
  • 5.0.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

In the meantime, consider restricting account creation and authentication to trusted users only and limit exposure of the MQTT broker to untrusted networks.

Description

In Meari IoT Cloud MQTT Broker deployments running EMQX 4.x, any authenticated low-privilege account can subscribe to global wildcard topics and receive telemetry from devices the user does not own. The broker enforces publish restrictions but does not enforce equivalent subscribe authorization at per-device scope.

References

Community reviews

Loading reviews…