Security readout for executives and security teams
Plain-English summary
Affected Zbtlink router firmware contains a built-in remote-control implant that starts automatically with root privileges. It repeatedly contacts a hardcoded server and can execute received commands without authentication. A compromised server, network-path attacker, or future controller of the fallback domain could obtain complete control of the router and potentially threaten connected networks.
Executive priority
Treat confirmed affected routers as potentially untrusted infrastructure and prioritize immediate isolation. Their position at the network boundary and unauthenticated root command capability create severe confidentiality, integrity, and availability risk. Replacement may be necessary unless the vendor provides a verifiably clean and supported remediation.
Technical view
The OpenWrt package librctl.so runs at boot as root while using the process name kworker. It calls home over unencrypted TCP, using ports 7000 and 7001, approximately every 35 seconds. Received strings reach popen(), and a reserved command enables an interactive root shell. The channel provides neither peer authentication nor transport encryption.
Likely exposure
Exposure is confirmed by the supplied data for 20 named Zbtlink firmware versions. The description claims every published product-line build contains the implant, but the structured affected list marks unlisted versions unaffected by default. Organizations should therefore prioritize exact model and firmware matching while treating the broader scope claim as requiring verification.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not listed as KEV. Nevertheless, deployed devices automatically initiate the control connection, requiring no inbound listening port or user interaction. Exploitation could become possible through control of the hardcoded infrastructure or interception of its unauthenticated cleartext traffic.
Researcher notes
CWE-506 appropriately characterizes the embedded malicious functionality. Important properties are boot persistence, uid 0 execution, kernel-thread-style process masquerading, popen()-based command handling, and an unauthenticated cleartext callback architecture. Scope evidence is internally awkward: the narrative alleges every published build, while the structured record enumerates specific versions and defaults others to unaffected.
Mitigation direction
- Disconnect or isolate confirmed affected routers from sensitive and untrusted networks.
- Restrict outbound TCP ports 7000 and 7001 where operationally safe.
- Monitor and block identified hardcoded command infrastructure using verified indicators from the advisory.
- Seek current vendor guidance on clean firmware, replacement, or supported remediation.
- Consider replacing affected devices if trustworthy remediation cannot be verified.
Validation and detection
- Inventory Zbtlink router models and compare installed firmware against the 20 listed versions.
- Inspect firmware and running processes for librctl.so and suspicious root-owned kworker naming.
- Review network telemetry for recurring outbound TCP connections on ports 7000 or 7001.
- Check for connection attempts occurring approximately every 35 seconds.
- After remediation, confirm the package, boot persistence, and callback traffic are absent.
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-506: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-66747 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
2 official scoresWe 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.9VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
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
- VulnCheck Research BlogCVE reference, VulnCheck · technical-description, exploit
- Vendor Firmware Download PageCVE reference, VulnCheck · product
- Upstream Open Source rctlCVE reference, VulnCheck
- VulnCheck AdvisoryCVE reference, VulnCheck · third-party-advisory
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.
Embedded Malicious Code
Embedded Malicious Code represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.