CVE-2026-49186
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe local MQTT broker does not enforce topic-level Access Control Lists (ACLs). This allows any client to subscribe using wildcard characters (# or +) to enumerate hidden network devices or publish rogue control commands.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe local MQTT broker fails to enforce topic-level Access Control Lists (ACLs), permitting any client to subscribe using wildcard characters (# or +). This allows unauthenticated clients to enumerate hidden network devices by subscribing to all topics and publish unauthorized control commands to any topic.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= m6e_ai_1.00.000019CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify device model and firmware versionAccess the device admin interface or check system information to confirm the device is Acer Connect M6e 5g and note the installed firmware version (e.g., m6e_ai_1.00.000019 or earlier)Affected if The device is Acer Connect M6e 5g with firmware version m6e_ai_1.00.000019 or earlier
-
Locate the MQTT broker serviceCheck running processes or services on the device for an MQTT broker daemon (commonly mosquitto or similar). Inspect the device filesystem for MQTT configuration files typically located in /etc/mosquitto/ or similar paths.Affected if An MQTT broker service is running on the device without proper ACL configuration files present
-
Review MQTT broker ACL configurationExamine the MQTT broker configuration files for any ACL definitions. Look for patterns like 'acl_file' directives or access control list entries that define topic-level permissions for clients.Affected if No ACL file is defined or the ACL configuration is missing topic-level restrictions for subscribe/publish operations
-
Test for wildcard subscription vulnerabilityConnect an MQTT client to the broker and attempt to subscribe using wildcard characters, such as topic '#' or '+/sensor/data' or 'home/#'. Observe if the broker accepts these wildcard subscriptions without rejecting them.Affected if The broker allows subscription to wildcard topics (# or +) without access control enforcement, returning success for unauthorized wildcard subscriptions
A user is affected if they have an Acer Connect M6e 5g device running firmware m6e_ai_1.00.000019 or earlier with an exposed MQTT broker that permits wildcard topic subscriptions without ACL enforcement.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement and enforce topic-level ACLs that restrict wildcard subscriptions to authorized clients only, combined with proper authentication. Regularly audit ACL rules to ensure least-privilege access.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-49186 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-49186 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data