CVE-2026-1157
Remote Buffer Overflow in Totolink LR350 setWiFiEasyCfg Function
Publication date: 2026-01-19
Last updated on: 2026-01-19
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| totolink | lr350 | 9.3.5u.6369_b20220309 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-119 | The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data. |
| CWE-120 | The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-1157 is a critical buffer overflow vulnerability in the Totolink LR350 router firmware version 9.3.5u.6369_B20220309. It exists in the setWiFiEasyCfg function within the /cgi-bin/cstecgi.cgi script. The vulnerability arises because the 'ssid' argument is processed without proper bounds checking, leading to a stack-based buffer overflow. This allows an attacker to remotely exploit the device without authentication, potentially executing arbitrary code or causing denial of service. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing a remote attacker to compromise the confidentiality, integrity, and availability of the affected Totolink LR350 router. Exploiting the buffer overflow can lead to arbitrary code execution or denial of service, potentially disrupting network connectivity and exposing sensitive information. Since the exploit is publicly available and easy to use, the risk of attack is significant. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
No known countermeasures or patches have been reported for this vulnerability. Immediate mitigation may require replacing the affected Totolink LR350 router device or avoiding exposure of the vulnerable endpoint remotely. [1]