PatchSiren cyber security CVE debrief
CVE-2026-105285 Totolink CVE debrief
A security vulnerability has been detected in Totolink A3002MU 1.0.0-B20230403.1455. This affects an unknown function of the file /boafrm/formIpQoS of the component QoS Rule Handler. The manipulation of the argument addQos/comment/entry_name leads to stack-based buffer overflow. Remote exploitation of the attack is possible. The exploit has been disclosed publicly and may be used.
- Vendor
- Totolink
- Product
- A3002MU
- CVSS
- CRITICAL 9.3
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-05
- Original CVE updated
- 2026-10-05
- Advisory published
- 2026-10-05
- Advisory updated
- 2026-10-05
Who should care
Defenders responsible for Totolink A3002MU devices, especially those with publicly accessible QoS Rule Handler interfaces, should assess exposure to this vulnerability and prioritize verification and potential remediation.
Why it matters
Defenders should prioritize verifying exposure of Totolink A3002MU devices to this stack-based buffer overflow vulnerability, especially those with publicly accessible QoS Rule Handler interfaces, and assess potential remediation needs.
- Verify exposure of Totolink A3002MU devices to this vulnerability
- Assess the QoS Rule Handler interface for public accessibility
- Monitor for potential exploitation attempts
- Remediation may be required to prevent exploitation
Technical summary
The vulnerability affects the QoS Rule Handler component of Totolink A3002MU 1.0.0-B20230403.1455. The manipulation of the argument addQos/comment/entry_name leads to stack-based buffer overflow, allowing remote attackers to exploit the vulnerability. This vulnerability has been publicly disclosed and may be used by attackers. Defenders should prioritize verifying exposure of Totolink A3002MU devices to this vulnerability, especially those with publicly accessible QoS Rule Handler interfaces, and assess potential remediation needs.
Defensive priority
Defenders should prioritize verifying exposure of Totolink A3002MU devices to this vulnerability, especially those with publicly accessible QoS Rule Handler interfaces.
Recommended defensive actions
- Verify exposure of Totolink A3002MU devices to this vulnerability
- Assess the QoS Rule Handler interface for public accessibility
- Monitor for potential exploitation attempts
- Apply vendor patches or updates to affected systems
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
Evidence notes
The CVE record and NVD entry provide details on the vulnerability, but the vendor and affected versions are not clearly stated. Further verification is needed to determine the scope of the vulnerability.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-105285 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-105285
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-105285 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-105285
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://gist.github.com/H3rmesk1t/b68352b011bc2825adc85cf336c25dfb
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/cve/CVE-2026-105285
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/submit/977224
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/vuln/413466
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/vuln/413466/cti
-
Source reference
Unverified legacy reference
URL: https://www.totolink.net/
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.