Security readout for executives and security teams
Plain-English summary
A critical access-control flaw in TOTOLINK T6 firmware 4.1.5cu.748_B20211015 may let an unauthenticated attacker submit malicious quality-of-service settings through MQTT. Successful abuse could compromise confidentiality, integrity, and availability. The sources do not establish how commonly the vulnerable broker is reachable or whether a corrected firmware exists.
Executive priority
Treat confirmed deployments as an immediate remediation priority because exploitation reportedly requires no authentication or user action and could cause complete device compromise. First identify affected firmware and restrict broker reachability. Escalate vendor contact if no verified correction is available; the supplied sources do not name a patch or confirmed fixed release.
Technical view
CVE-2026-51770 affects the sendToMasterQosConfig function associated with the cs_broker component. A crafted MQTT message can forward attacker-controlled QoS configuration to the master without authentication. It is classified as CWE-284 and scored CVSS 3.1: 9.8, reflecting network reachability, low complexity, no privileges, no user interaction, and potentially complete impact.
Likely exposure
Potential exposure is limited to TOTOLINK T6 devices running firmware 4.1.5cu.748_B20211015 whose MQTT cs_broker component is reachable by an attacker. The bundle does not identify default broker accessibility, required network position, deployment prevalence, or other affected versions. Confirm firmware and network reachability rather than assuming every T6 device is exploitable.
Exploitation context
The bundle reports an unauthenticated, network-based attack path using a crafted MQTT message. It contains no CISA KEV listing and provides no cited evidence of active exploitation. Public researcher coordination pages are referenced, but the supplied information does not establish exploit reliability, observed attacks, or proof-of-concept availability.
Researcher notes
The record attributes the issue to incorrect access control in sendToMasterQosConfig and cs_broker. Structured affected-product fields are listed as “n/a,” while the title and description identify TOTOLINK T6 firmware 4.1.5cu.748_B20211015. This inconsistency limits certainty about the full affected range. Avoid extending impact to other models or releases without vendor or CVE updates.
Mitigation direction
- Check TOTOLINK guidance for corrected firmware or vendor-approved mitigations.
- Restrict MQTT broker access to trusted management hosts and networks.
- Block untrusted access to cs_broker at network boundaries.
- Isolate affected routers until remediation status is confirmed.
- Back up configuration and monitor for unauthorized QoS changes.
Validation and detection
- Inventory TOTOLINK T6 devices and record their exact firmware versions.
- Confirm whether firmware 4.1.5cu.748_B20211015 is present.
- Review firewall paths and broker bindings for attacker-reachable MQTT access.
- Inspect configuration and logs for unexpected QoS changes or MQTT activity.
- Verify any replacement firmware against current TOTOLINK guidance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-51770 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.totolink.net/home/menu/detail/menu_listtpl/download/id/190/ids/36.htmlCVE reference, mitre
- https://www.totolink.net/CVE reference, mitre
- https://github.com/DarkBoulder/CVE-Vendor-Coordination/blob/main/TOTOLINK/README.mdCVE reference, mitre
- https://github.com/ShengWu00/CVE-Vendor-Coordination/blob/main/TOTOLINK/README.mdCVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.