CVE-2026-26731
Stack-Based Buffer Overflow in TOTOLINK A3002RU Router Firmware
Publication date: 2026-02-17
Last updated on: 2026-03-16
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| totolink | a3002ru_firmware | 2.1.1-b20211108.1455 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-787 | The product writes data past the end, or before the beginning, of the intended buffer. |
| CWE-121 | A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a stack-based buffer overflow found in the TOTOLINK A3002RU router, specifically in version V2.1.1-B20211108.1455. It occurs via the 'routernamer' parameter in the formDnsv6 function.
How can this vulnerability impact me? :
A stack-based buffer overflow can allow an attacker to execute arbitrary code, potentially leading to unauthorized access, system crashes, or control over the affected device.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves a stack-based buffer overflow via the routernamer parameter in the formDnsv6 function of TOTOLINK A3002RU V2.1.1-B20211108.1455. Detection would typically involve monitoring for unusual or malformed HTTP requests targeting the formDnsv6 endpoint with suspicious routernamer parameter values.
Specific commands or detection scripts are not provided in the available resources.
What immediate steps should I take to mitigate this vulnerability?
No explicit mitigation steps are detailed in the provided context or resources.
General best practices would include restricting access to the vulnerable device, applying any available firmware updates from the vendor, and monitoring network traffic for exploitation attempts.