/

CVE-2026-79390

Severity:

HIGH RISK

(7.5)

Cleartext MQTT Transmission (CWE-284) in Trueview TI8161

CVE-2026-79390

Deferred

Vulnerability type

Category:

Cleartext Transmission

CWE:

CWE-284

Impact:

Information Disclosure

Severity:

HIGH RISK

(7.5)

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 TI8161 transmits MQTT communications in plaintext over TCP port 1883, allowing network observers to read device and operational information.

An unauthenticated attacker with access to the same network segment may intercept traffic and obtain device identifiers, message metadata, and control-related data.

Affected context

The issue occurs in deployments where the Trueview TI8161 device uses MQTT over unencrypted TCP port 1883. It becomes risky when MQTT traffic traverses a network segment that an unauthorized party can monitor and when sensitive device or operational information is included in the messages.

Exploit preconditions

  • Attack surface: MQTT network communications over TCP port 1883
  • Required access: Unauthenticated access to the same network segment or a position capable of observing the traffic
  • Trigger point: Transmission of MQTT messages containing device or operational information
  • Why exploitation is possible: Plaintext communications do not provide confidentiality, allowing observable traffic to be read by a network-level attacker

Why this happens

The underlying issue is the transmission of potentially sensitive MQTT data without transport encryption. Plaintext application traffic can expose message contents and metadata to parties that can monitor the network path.

This finding is associated with CWE-284: Improper Access Control, reflecting insufficient protection of access to sensitive communications. The insecure pattern is allowing network-observable data to cross a trust boundary without adequate confidentiality controls.

Potential impact

  • An attacker may obtain device identifiers and message metadata
  • Operational information could be disclosed
  • Control-related topics or messages may reveal system behavior
  • Exposed data could support further targeting or unauthorized manipulation attempts

General mitigation guidance

Mitigation generally focuses on reducing the trust placed in the network and protecting MQTT communications in transit.

Common defensive patterns include:

  • Using encrypted MQTT transport with certificate-based server authentication where supported
  • Avoiding plaintext MQTT listeners for sensitive or production traffic
  • Restricting broker and device connectivity to explicitly authorized network paths
  • Minimizing sensitive information in topics, payloads, and metadata
  • Applying least-privilege permissions to MQTT topics and administrative interfaces
  • Segmenting device networks and monitoring access to messaging infrastructure

How teams detect issues like this

Organizations can assess this issue through:

  • Network monitoring for MQTT sessions on plaintext TCP port 1883
  • Configuration reviews for unencrypted broker and device endpoints
  • Traffic inspection in controlled environments to verify whether payloads and metadata are readable
  • Code and architecture reviews for MQTT clients that lack transport encryption or certificate validation
  • Policy enforcement requiring encrypted protocols for sensitive device communications
  • Automated security review tools that flag cleartext network protocols and unrestricted messaging endpoints

Sources

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

Frequently asked

questions

It is network-adjacent rather than directly Internet-wide. An attacker generally needs access to the same network segment or another position where MQTT traffic can be observed.

The described interception does not require authentication to the device or MQTT service, but network access sufficient to observe the traffic is required.

Protect MQTT communications with encrypted transport and authenticated endpoints, while restricting access to authorized clients and network paths.

Establish policies that prohibit plaintext protocols for sensitive data, review device and broker configurations, segment operational networks, and continuously monitor for unencrypted MQTT traffic.

Find out what's already
exploitable in your codebase.