/

CVE-2026-51611

Severity:

CRITICAL RISK

(9.8)

Access Control (CWE-284) in TOTOLINK T6 startSlaveReboot

CVE-2026-51611

Deferred

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-284

Impact:

Unauthorized device reboot 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 improper access control vulnerability in the TOTOLINK T6 router allows unauthenticated attackers to trigger the startSlaveReboot function through a crafted MQTT message. Successful exploitation can force the device to reboot, disrupting network availability when MQTT input is reachable and insufficiently protected.

Affected context

The issue occurs in the TOTOLINK T6 4.1.5cu.748_B20211015 firmware within the startSlaveReboot function. Risk is higher when the device accepts MQTT messages from an attacker-controlled or insufficiently restricted network path and the function does not require effective authentication or authorization.

Exploit preconditions

  • Attack surface: MQTT message handling on the router
  • Required access: No authentication is required when the vulnerable message path is reachable
  • Trigger point: Processing of a crafted MQTT message that invokes the startSlaveReboot function
  • Why exploitation is possible: The function does not adequately verify whether the requester is authorized to perform a reboot

Why this happens

The underlying bug is an authorization failure in a privileged device-management function. The MQTT handler permits a reboot operation without enforcing an appropriate authentication and authorization decision, mapping to CWE-284: Improper Access Control. The insecure pattern is exposing a state-changing administrative action through a message interface without reliably checking caller identity, privilege, and operation scope.

Potential impact

  • An attacker may repeatedly reboot the router
  • Network connectivity and dependent services could be interrupted
  • Users may experience denial of service
  • Repeated disruption could interfere with monitoring, recovery, or administrative operations

General mitigation guidance

Mitigation generally focuses on ensuring that every state-changing management operation is protected by centralized authentication and authorization controls.

Common defensive patterns include:

  • Requiring authenticated, authorized sessions for reboot operations
  • Restricting MQTT brokers, topics, and clients to trusted management networks
  • Applying deny-by-default access policies to administrative message handlers
  • Separating management interfaces from ordinary network traffic
  • Enforcing least privilege for service accounts and device-management processes
  • Adding replay, rate, and abuse controls for disruptive administrative actions
  • Failing closed when identity, topic permissions, or authorization state cannot be established

How teams detect issues like this

Organizations can identify similar issues through:

  • Static analysis of MQTT handlers and other message consumers for direct calls to privileged functions
  • Code review checks for missing authentication, authorization, topic validation, or privilege checks
  • Tests that submit management messages from unauthenticated and lower-privilege clients
  • MQTT broker policy reviews covering client identity, topic ACLs, and network exposure
  • Runtime monitoring for unexpected reboot commands, repeated restart events, and unusual MQTT activity
  • Automated security testing and neutral code-review tools that flag externally reachable state-changing operations without access checks

Sources

SourceLink
github.comgithub.com/DarkBoulder/CVE-Vendor-Coordination/blob/main/TOTOLINK/20260416_T6_vuln_report.pdf
github.comgithub.com/DarkBoulder/CVE-Vendor-Coordination/blob/main/TOTOLINK/20260424_T6_confirm.pdf
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, when the vulnerable MQTT message path is reachable by an attacker. The attack does not require local access if network controls expose that path.

No authentication is required according to the vulnerability description, provided the attacker can send a suitable MQTT message to the affected interface.

Protect the reboot operation with mandatory authentication, explicit authorization, and deny-by-default MQTT topic and client policies.

Treat every message-triggered administrative action as privileged, test it with unauthorized clients, restrict management-plane exposure, and monitor for abnormal device-control activity.

Find out what's already
exploitable in your codebase.