/

CVE-2026-51767

Severity:

CRITICAL RISK

(9.8)

Broken Access Control (CWE-284) in TOTOLINK T6 MQTT

CVE-2026-51767

Deferred

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-284

Impact:

Unauthorized device control and denial of service

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 allows unauthenticated attackers to send crafted MQTT messages that invoke the recvClearPairCfg function. Successful exploitation may reset the device's pairing state and force a reboot, disrupting availability and device configuration.

Affected context

The issue occurs in TOTOLINK T6 4.1.5cu.748_B20211015 deployments where the cs_broker MQTT component can receive messages that reach the recvClearPairCfg function without adequate authorization checks. Risk is greatest when the MQTT service is reachable by untrusted networks or when broker access is not otherwise restricted.

Exploit preconditions

  • Attack surface: The device's MQTT service and cs_broker component
  • Required access: Network reachability to the relevant MQTT interface; authentication may not be required
  • Trigger point: Processing of a crafted MQTT message by recvClearPairCfg
  • Why exploitation is possible: The function permits sensitive pairing-state and reboot operations without sufficiently verifying the caller's authorization

Why this happens

The underlying flaw is an authorization failure in a security-sensitive message handler. The recvClearPairCfg function processes a request capable of changing pairing state and rebooting the device without enforcing an appropriate authentication or authorization decision. This behavior maps to CWE-284, Improper Access Control, because a protected operation is exposed to an insufficiently trusted requester.

Potential impact

  • An unauthenticated attacker could reset the device's pairing state
  • The device could be rebooted unexpectedly
  • Connected services or users may experience loss of availability
  • Pairing disruption could require administrative recovery or reconfiguration
  • Repeated requests could cause persistent operational instability

General mitigation guidance

Mitigation generally focuses on protecting administrative MQTT operations and

reducing exposure of device-management interfaces.

Common defensive patterns include:

  • Require strong authentication and explicit authorization for pairing-state changes and reboot actions
  • Apply deny-by-default access controls to MQTT topics and management commands
  • Restrict broker and device-management connectivity to trusted network segments
  • Separate ordinary telemetry topics from privileged control topics
  • Validate message origin, session state, and authorization before invoking sensitive handlers
  • Run management functions with the minimum privileges needed for their operation
  • Monitor and rate-limit repeated pairing-reset or reboot requests

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis and code review checks for sensitive handlers lacking authorization gates
  • Review of MQTT topic permissions and broker access-control policies
  • Testing unauthenticated access to administrative commands in isolated environments
  • Network monitoring for unexpected pairing-reset or reboot message activity
  • Audit logging that records the requester, topic, authorization result, and operation outcome
  • Automated security review tools that identify externally reachable management functions without access checks

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. An attacker may be able to exploit it over the network when the device's

MQTT service is reachable and accepts the relevant message.

The vulnerability description indicates that authentication is not required.

Network reachability to the exposed MQTT interface remains a prerequisite.

Enforce authentication and per-command authorization before allowing pairing

changes or reboot operations, while limiting MQTT exposure to trusted clients.

Treat all externally received MQTT messages as untrusted, use deny-by-default

topic policies, protect privileged handlers with centralized authorization, and

test management commands under unauthenticated and low-privilege conditions.

Find out what's already
exploitable in your codebase.