CVE-2026-79391
—Unauthenticated MQTT Broker Access in Trueview 6.0.23.4
Trueview 6.0.23.4 runs its MQTT broker on TCP port 1883 with no authentication, a missing-authentication flaw (CWE-306). Any remote attacker who can reach the port can open an MQTT session and perform unauthorized publish or subscribe operations without credentials. This could let an attacker read data flowing through the broker (confidentiality), inject or forge messages to subscribed clients (integrity), and potentially disrupt message delivery (availability), consistent with the critical 9.8 CVSS score. All deployments of Trueview 6.0.23.4 that expose TCP port 1883 over the network are affected, particularly those reachable from the internet or shared network segments. No public proof-of-concept, CISA KEV listing, or confirmed in-the-wild exploitation is known, and EPSS estimates only a 0.4% probability of exploitation in the next 30 days.
What to do: Audit whether TCP port 1883 on Trueview devices is reachable from untrusted networks or the internet, and restrict access with firewall rules, ACLs, or a VPN. Upgrade to a fixed release when one becomes available (no fixed version is specified in the available data), and if the broker supports it, enable MQTT authentication or place the service behind an authenticated proxy or TLS-protected gateway.
| Trueview (MQTT service) | 6.0.23.4 (other 6.0.x versions may also be affected; not confirmed in the data) |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
No authentication exists in the MQTT service of Trueview 6.0.23.4. The MQTT broker accepts client connections on TCP port 1883 without requiring authentication, allowing a remote attacker with network access to establish an MQTT session and perform unauthorized publish or subscribe operations.
- Weakness
- CWE-306
- Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
In the news0 stories
No ingested article mentions this CVE yet.