/

CVE-2026-51760

Severity:

CRITICAL RISK

(9.8)

Improper Access Control (CWE-284) in TOTOLINK T6 Mesh

CVE-2026-51760

Deferred

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-284

Impact:

Unauthorized firmware update triggering and potential mesh-wide service disruption

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

A critical access-control vulnerability in the TOTOLINK T6 mesh firmware allows unauthenticated attackers to trigger firmware update activity across connected mesh slave devices by sending a crafted MQTT message.

Successful exploitation could cause unauthorized device changes, widespread service disruption, or coordinated compromise of mesh nodes when the MQTT broker is reachable by an attacker.

Affected context

The issue occurs in deployments using TOTOLINK T6 devices with firmware version 4.1.5cu.748_B20211015, where the informSyncUpgfw function processes update-related commands through the cs_broker MQTT component. Risk is increased when unauthenticated clients can reach the broker or when broker messages are not adequately authenticated and authorized before being acted upon by mesh slave devices.

Exploit preconditions

  • Attack surface: The cs_broker MQTT messaging component and its firmware-update command handling
  • Required access: Network access sufficient to submit MQTT messages; valid credentials may not be required
  • Trigger point: Processing of a crafted message by the informSyncUpgfw function
  • Why exploitation is possible: The update-related operation does not sufficiently verify whether the message sender is authorized to request firmware activity across mesh slaves

Why this happens

The vulnerability is caused by an authorization failure in a privileged firmware-management operation. The informSyncUpgfw function appears to trust an MQTT-triggered request without enforcing adequate authentication, authorization, or command-scope checks.

This maps to CWE-284: Improper Access Control, where a security-sensitive function does not correctly restrict access to authorized users or components. Because the operation can affect multiple mesh slaves, insufficient access control may turn a single untrusted message into a fleet-wide action.

Potential impact

  • Unauthorized firmware update activity across mesh slave devices
  • Device restarts, degraded availability, or extended service disruption
  • Inconsistent firmware state across the mesh network
  • Potential firmware integrity compromise if update sources or validation controls are also weakened
  • Expanded attack impact through coordinated actions against multiple connected devices

General mitigation guidance

Mitigation generally focuses on enforcing authorization at the MQTT command boundary and separating ordinary messaging from privileged firmware-management operations.

Common defensive patterns include:

  • Require strong client authentication and topic-level authorization for MQTT operations
  • Enforce explicit authorization checks inside firmware-update handlers rather than relying only on broker configuration
  • Validate message structure, origin, scope, freshness, and intended target before performing update activity
  • Use signed firmware, trusted update sources, and integrity verification before installation
  • Limit update permissions to narrowly scoped administrative identities and apply least privilege across mesh roles
  • Isolate management interfaces and avoid exposing broker services to untrusted networks
  • Add rate limits, approval controls, and audit logging for fleet-wide firmware operations

How teams detect issues like this

Detection can combine code review, runtime monitoring, and configuration policy enforcement.

Useful approaches include:

  • Static analysis searches for MQTT handlers that invoke firmware, reboot, or configuration operations without nearby authorization checks
  • Code review checks for trust decisions based solely on message presence, topic names, or client reachability
  • Tests that submit privileged messages from unauthenticated, unauthorized, and cross-scope clients
  • Broker policy reviews covering client authentication, topic ACLs, publish permissions, and subscription permissions
  • Monitoring for unusual firmware-update message volume, broad target selection, repeated triggers, or update requests from unexpected clients
  • Automated security testing and policy tools that flag unauthenticated access to administrative message paths

Sources

SourceLink
github.comgithub.com/DarkBoulder/CVE-Vendor-Coordination/blob/main/TOTOLINK/README.md
github.comgithub.com/ShengWu00/CVE-Vendor-Coordination/blob/main/TOTOLINK/README.md
totolink.nettotolink.net/
totolink.nettotolink.net/home/menu/detail/menu_listtpl/download/id/190/ids/36.html

Frequently asked

questions

Yes, potentially. An attacker may be able to exploit it over the network if the cs_broker MQTT component is reachable and accepts the relevant message without requiring effective authentication.

The description indicates that authentication is not required. The practical scope still depends on network reachability, broker exposure, and any external segmentation controls.

Enforce authenticated, topic-scoped authorization for MQTT clients and repeat the authorization decision within the firmware-update handler. Firmware authenticity and integrity checks should also remain mandatory.

Treat firmware-management messages as privileged administrative commands, apply least privilege, test unauthorized message paths, restrict broker exposure, and monitor fleet-wide update activity.

Find out what's already
exploitable in your codebase.