Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach T6 MQTT broker on segment
-
DeliveryCraft malicious QoS MQTT message
-
ExploitPublish to cs_broker sendToMasterQosConfig
-
ExecutionMaster applies settings without auth
-
ImpactTraffic prioritization manipulated/degraded
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Access control enforcement
MITRE ATT&CK
1 technique across 1 tactic: Defense Evasion The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires network reachability to the T6's internal MQTT broker (the cs_broker component) and the ability to publish a crafted MQTT message to the sendToMasterQosConfig topic/handler; no credentials, user interaction, or non-default feature toggles are described (PR:N/UI:N). The practical limiting factor is broker reachability: cs_broker is an internal mesh/cluster service, so exploitation is realistic for an attacker on the LAN, guest, or mesh segment, or against a device whose broker port is exposed to the WAN - a remote Internet attacker only qualifies if that port is externally reachable. Affected build is specifically firmware 4.1.5cu.748_B20211015 on the TOTOLINK T6. |
| Impact | The published CVSS 9.8 (AV:N/AC:L/PR:N/UI:N, C:H/I:H/A:H) overstates real-world impact: the described action is forwarding attacker-controlled QoS settings, which is a write/config-tampering primitive affecting integrity (and marginally availability via traffic degradation), not a disclosure of sensitive data - so C:H is not justified by the description; a more defensible impact is C:N/I:H/A:L. The MITRE-sourced CVSS network vector is also optimistic in practice: MQTT/cs_broker is typically an internal LAN/mesh service, so 'network' exploitation usually presumes the attacker already has L2/LAN reachability to the broker rather than arbitrary Internet access, unless the broker port is exposed on WAN. EPSS is low (0.18%, 7th percentile) and there is no KEV listing and no identified public PoC, so this reads as a genuine unauthenticated-config-tampering weakness that is nonetheless a low-urgency, targeted-risk item rather than a mass-exploited emergency. Because the flaw requires no credentials and can degrade or manipulate network traffic prioritization for every device behind the router, any operator running affected T6 units on an untrusted or bridged segment should still remediate promptly. The 'Authentication Bypass' tag is a loose fit - this is missing access control on an unauthenticated handler rather than a bypass of an existing auth mechanism. |
| Exploit ScenarioDerived | An attacker on the same LAN/Wi-Fi segment (or reaching an internet-exposed broker) crafts and publishes an MQTT message to the T6's cs_broker targeting the sendToMasterQosConfig handler with malicious QoS parameters. The master node accepts and applies the settings without authenticating the sender, letting the attacker reshape or degrade traffic prioritization for downstream clients. No public PoC is currently identified, but the low complexity (AC:L) and lack of authentication make weaponization straightforward for an attacker with broker reachability. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 02, 2026
Unauthenticated QoS configuration injection in the TOTOLINK T6 router (firmware 4.1.5cu.748_B20211015) lets remote attackers push attacker-controlled Quality-of-Service settings to the master node by sending a crafted MQTT message to the cs_broker component's sendToMasterQosConfig handler. Because the handler performs no authentication or access-control check, any party able to reach the MQTT broker can alter traffic-shaping/prioritization policy across the managed mesh. No public exploit identified at time of analysis, and EPSS is low (0.18%), indicating no observed mass exploitation yet.
RemediationAI
No vendor-released patched firmware version is identified in the available data, so treat mitigation as compensating-control-driven: check the TOTOLINK support/download page (https://www.totolink.net/home/menu/detail/menu_listtpl/download/id/190/ids/36.html) for a firmware build newer than 4.1.5cu.748_B20211015 and apply it if published. Until then, restrict reachability to the cs_broker MQTT service by ensuring the MQTT broker port is not exposed on the WAN interface and is firewalled from untrusted VLANs/guest networks (trade-off: none for typical single-router deployments, but may disrupt legitimate mesh coordination if slave nodes traverse the filtered segment). Isolate mesh/agent nodes onto a dedicated management VLAN so only trusted peers can publish to the broker, and disable remote/WAN management. For high-assurance environments where firmware cannot be updated, consider replacing affected T6 units, since the missing access control cannot be fully closed by configuration alone. Monitor the coordination advisories at https://github.com/DarkBoulder/CVE-Vendor-Coordination/blob/main/TOTOLINK/README.md for a fixed release.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The T6 is a mesh-capable consumer/SOHO Wi-Fi router that uses an internal MQTT bus (the cs_broker component) to coordinate configuration between the master node and slave/agent nodes. The sendToMasterQosConfig function subscribes to or accepts MQTT-published QoS configuration payloads and relays them to the master for application. The root cause is CWE-284 (Improper Access Control): the MQTT topic/handler trusts any publisher and does not verify that the sender is an authenticated, authorized cluster peer, so an outsider who can publish to the broker is treated identically to a legitimate node. This is the same architectural weakness seen across a cluster of T6 MQTT/cs_broker handlers (e.g., freeStaClient, guest_wifi_sync), where individual command functions inherit the broker's missing authentication.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Unauthenticated low-complexity MQTT write to config (PR:N/AC:L); action is config tampering so I:H, minor traffic degradation A:L, and no disclosure so C:N.
Primary rating from Vendor (mitre).
CVSS VectorVendor: mitre
Lifecycle Timeline
3DescriptionCVE.org
Incorrect access control in the sendToMasterQosConfig function of TOTOLINK T6 4.1.5cu.748_B20211015 allows unauthenticated attackers to forward attacker-controlled QoS settings to the master via sending a crafted MQTT message to the cs_broker component..
Executive ViewAI
TOTOLINK T6 routers (firmware 4.1.5cu.748_B20211015) contain a critical remote vulnerability allowing attackers to inject and alter QoS traffic-shaping policies across managed router meshes without authentication. Organizations operating these devices in mesh deployments face network disruption and traffic manipulation risks, with no vendor patch currently available. Immediate containment and evaluation of replacement options is required for critical infrastructure protection.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Restrict MQTT broker network access to affected TOTOLINK T6 routers from trusted management interfaces only; (2) Monitor MQTT traffic and event logs for suspicious sendToMasterQosConfig messages or unexpected QoS configuration changes; (3) Implement network segmentation to isolate affected routers and limit attacker reach; (4) Deploy configuration change alerting to detect unauthorized QoS policy modifications in real-time; (5) Maintain current backup of router configurations to enable rapid recovery if policies are altered.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-69380
GHSA-c6w3-3vcp-m3h3
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB