LiveActive security incident?Get immediate response
CVE Record

CVE-2026-51769: Incorrect access control in the remoteCloudUpdateCheck function of TOTOLINK T6 4.1.5cu.748_B20211015 allows...

Incorrect access control in the remoteCloudUpdateCheck function of TOTOLINK T6 4.1.5cu.748_B20211015 allows unauthenticated attackers to restart the cloud update check workflow via sending a crafted MQTT message to the cs_broker component.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A flaw in TOTOLINK T6 firmware 4.1.5cu.748_B20211015 may let an unauthenticated attacker send an MQTT message that restarts the router’s cloud-update checking workflow. The record rates it critical, but the supplied description does not explain how restarting that workflow produces the claimed confidentiality, integrity, and availability impact.

Executive priority

Prioritize immediate identification and containment of matching devices, especially those reachable from untrusted networks. The critical score and unauthenticated trigger justify urgent review, although the source bundle leaves the full business impact and patch status unclear. Require owners to document exposure, compensating controls, and a vendor-supported remediation or replacement decision.

Technical view

The remoteCloudUpdateCheck function in the cs_broker component lacks correct access control. An unauthenticated network attacker can reportedly trigger the cloud-update check workflow using a crafted MQTT message. The record assigns CVSS 3.1 score 9.8 and CWE-284. The structured affected-product fields are unspecified, while the title and description identify TOTOLINK T6 firmware 4.1.5cu.748_B20211015.

Likely exposure

Potential exposure is limited to TOTOLINK T6 devices running the named firmware where an attacker can reach the relevant MQTT messaging path. The bundle does not establish default reachability, Internet exposure, other affected releases, or whether authentication elsewhere limits access. Confirm device model, exact firmware, broker configuration, and network accessibility.

Exploitation context

The bundle does not show CISA KEV listing or provide evidence of active exploitation. Public coordination references exist, but no confirmed exploitation prevalence, proof-of-concept status, or attack observations are established here. Treat the unauthenticated, network-reachable design and 9.8 score seriously without describing exploitation as active.

Researcher notes

The CVSS vector claims high confidentiality, integrity, and availability impact, but the description only documents unauthorized restarting of an update-check workflow. Further impact should not be assumed without supporting evidence. Key unknowns include MQTT reachability, message authorization boundaries, persistence, affected-version range, firmware correction status, and whether workflow retriggering enables consequences beyond disruption.

Mitigation direction

  • Check TOTOLINK guidance and the firmware download page for an updated release or vendor-prescribed mitigation.
  • Restrict the device and its MQTT-related services from untrusted networks and unnecessary Internet access.
  • Limit broker access to explicitly authorized systems using network controls where operationally feasible.
  • Disable remote cloud-update functionality only if vendor guidance supports doing so safely.
  • Prioritize replacement if no supported remediation exists and exposure cannot be adequately restricted.

Validation and detection

  • Inventory TOTOLINK T6 devices and record their exact installed firmware versions.
  • Determine whether any device runs 4.1.5cu.748_B20211015.
  • Verify whether untrusted networks can reach the device’s MQTT or cs_broker communication path.
  • Review available device and network logs for unexpected or repeated cloud-update checks.
  • Confirm remediation against current TOTOLINK guidance, then retest network exposure and normal update behavior.
Prepared
Confidence
medium
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

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 lookup
cve · low confidence lookup

CVE-2026-51769 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
3Timeline events
1ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2026-51769Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-284 · source CWE mapping

Improper Access Control

Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.