/

CVE-2026-51769

Severity:

CRITICAL RISK

(9.8)

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

CVE-2026-51769

Deferred

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-284

Impact:

Unauthorized workflow control and potential 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

An improper access control vulnerability in the TOTOLINK T6 router allows unauthenticated attackers to restart the cloud update check workflow by sending a crafted MQTT message. The issue becomes risky when the MQTT broker accepts externally supplied messages without verifying the sender's authorization.

Affected context

The vulnerability occurs in the remoteCloudUpdateCheck function and its interaction with the cs_broker MQTT component. Deployments may be exposed when MQTT messages can reach the broker without authentication or authorization checks, allowing an unauthenticated party to influence the cloud update check workflow.

Exploit preconditions

  • Attack surface: MQTT messaging through the cs_broker component
  • Required access: No authenticated account may be required when the broker is externally reachable
  • Trigger point: Processing of a crafted message associated with remoteCloudUpdateCheck
  • Why exploitation is possible: The workflow accepts or acts on a control message without sufficiently verifying that the sender is authorized to request the operation

Why this happens

The underlying bug is a missing or ineffective authorization check on a privileged workflow control path. The remoteCloudUpdateCheck function appears to trust an MQTT-triggered request without binding it to an authenticated and authorized client, which maps to CWE-284: Improper Access Control. Insecure designs of this kind expose administrative actions through message handlers without enforcing least privilege at the operation boundary.

Potential impact

  • An attacker may repeatedly restart the cloud update check workflow
  • Router management or update-related services could experience disruption
  • Excessive workflow restarts could consume system resources
  • Repeated manipulation could interfere with normal cloud update behavior
  • The device may become more difficult to monitor or maintain during sustained abuse

General mitigation guidance

Mitigation generally focuses on enforcing authorization at every privileged MQTT message handler and reducing the trust placed in unauthenticated broker traffic.

Common defensive patterns include:

  • Require client authentication and topic-level authorization for control messages
  • Permit only narrowly defined, authenticated principals to invoke update-related workflows
  • Validate message structure, origin, freshness, and replay resistance before processing
  • Keep administrative MQTT topics separate from ordinary telemetry or device traffic
  • Apply rate limits and bounded retry behavior to workflow restart requests
  • Run update and broker components with the minimum privileges necessary
  • Deny external broker access by default and use explicit network allowlists where appropriate

How teams detect issues like this

Organizations can look for this issue through:

  • Static analysis and code review of MQTT callbacks that invoke administrative functions
  • Review signals showing privileged operations reachable before authentication or authorization
  • Tests that send messages from unauthenticated, unauthorized, and cross-device clients
  • Broker policy checks confirming topic permissions and client identity enforcement
  • Runtime monitoring for repeated cloud update workflow restarts or unusual MQTT publishers
  • Automated security review tools that identify externally reachable control paths 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

It can be remotely exploitable when the MQTT broker or its relevant message path is reachable by an unauthenticated attacker.

No authenticated account may be necessary if the broker accepts the triggering message without verifying client identity and authorization.

Require authenticated MQTT clients and enforce topic- and operation-level authorization before allowing any cloud update workflow control.

Treat every message-driven administrative action as privileged, apply deny-by-default broker policies, test unauthorized message paths, and monitor for abnormal workflow activity.

Find out what's already
exploitable in your codebase.