/

CVE-2026-79391

Severity:

CRITICAL RISK

(9.8)

Missing Authentication (CWE-306) in Trueview MQTT

CVE-2026-79391

Deferred

Vulnerability type

Category:

Missing Authentication

CWE:

CWE-306

Impact:

Unauthorized MQTT access and message manipulation

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Trueview 6.0.23.4 exposes an MQTT service on TCP port 1883 without requiring client authentication. A remote attacker with network access may connect to the broker and perform unauthorized publish or subscribe operations, potentially affecting connected devices and application data.

Affected context

The vulnerability occurs in Trueview deployments where the MQTT broker listens on TCP port 1883 and accepts client connections without verifying credentials or another authentication factor. Risk depends on network reachability: systems exposed to untrusted networks or broad internal segments may be more accessible to unauthorized clients.

Exploit preconditions

  • Attack surface: MQTT service exposed on TCP port 1883
  • Required access: Network connectivity to the broker; valid credentials are not required
  • Trigger point: Establishing an MQTT client session
  • Why exploitation is possible: The service accepts connections and MQTT operations without authenticating the client identity

Why this happens

The underlying issue is an access-control failure in which an externally reachable service does not require authentication before granting access to protected broker operations. This maps to CWE-306: Missing Authentication for Critical Function, because the MQTT service permits client sessions and publish or subscribe activity without establishing whether the requester is authorized.

Potential impact

  • An attacker could subscribe to sensitive MQTT topics
  • An attacker could publish forged, misleading, or malicious messages
  • Connected systems could act on unauthorized commands or data
  • Operational data could be disclosed or altered
  • The broker or dependent applications could experience disruption

General mitigation guidance

Mitigation generally focuses on requiring authentication for every MQTT client connection and limiting access to broker operations according to identity and role.

Common defensive patterns include:

  • Enabling strong client authentication and rejecting anonymous sessions
  • Applying topic-level authorization with least privilege
  • Restricting broker exposure through network segmentation and firewall policy
  • Using encrypted transport and managed credentials where supported
  • Separating read and write permissions for sensitive topics
  • Running dependent services with only the privileges they require

These controls reduce exposure even when an attacker can reach the MQTT listener.

How teams detect issues like this

Organizations can identify missing-authentication risks through:

  • Configuration reviews confirming that anonymous MQTT access is disabled
  • Network scans that identify reachable MQTT listeners on TCP port 1883
  • Broker logs showing client connections without authenticated identities
  • Static and infrastructure-as-code checks for anonymous listener settings
  • Code review signals where authentication middleware is absent from connection handling
  • Policy enforcement requiring authentication, authorization, and encrypted transport for messaging services

Neutral automated security review tools may help detect exposed listeners and permissive broker configurations.

Sources

SourceLink
github.comgithub.com/EmbdCDACHyd/CVE/blob/main/CVE-2026-79391/README.md

Frequently asked

questions

Yes, when the MQTT service is reachable over a network. Exploitation requires connectivity to the broker but does not require valid MQTT credentials.

The attacker needs network access to TCP port 1883. The absence of authentication allows a reachable client to establish a session and attempt publish or subscribe operations.

Require authentication before accepting MQTT sessions, enforce topic-level authorization, and restrict network access to trusted clients.

Use secure-by-default broker configurations, continuously review listener exposure, enforce identity-based access policies, and monitor connection and topic activity for anonymous or unexpected clients.

Find out what's already
exploitable in your codebase.