VYPR
Unrated severityNVD Advisory· Published Jun 9, 2026· Updated Jun 9, 2026

CVE-2026-36815

CVE-2026-36815

Description

Tenda W15E v15.11.0.10 has a buffer overflow in formSetNetCheckTools allowing DoS via crafted HTTP request.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Tenda W15E v15.11.0.10 has a buffer overflow in formSetNetCheckTools allowing DoS via crafted HTTP request.

Vulnerability

A buffer overflow vulnerability exists in the formSetNetCheckTools function of Shenzhen Tenda Technology Co., Ltd Tenda W15E version v15.11.0.10. The vulnerability is triggered when processing the hostName parameter, which is retrieved using websGetVar. The length of the hostName parameter is then used to copy data into a fixed-size buffer without proper bounds checking, leading to the overflow [1].

Exploitation

An attacker can exploit this vulnerability by sending a crafted HTTP request to the formSetNetCheckTools CGI endpoint. The request must include a hostName parameter with a value exceeding the allocated buffer size, for example, a string of 888 or more characters. This can be achieved without any special privileges or authentication, as the vulnerable path is directly reachable [1].

Impact

Successful exploitation of this buffer overflow vulnerability can lead to a Denial of Service (DoS) condition. This may manifest as a process crash or general device instability, rendering the affected Tenda W15E router inoperable for legitimate users [1].

Mitigation

No patched version or specific mitigation details have been disclosed in the available references. The vulnerability affects Tenda W15E v15.11.0.10 [1].

AI Insight generated on Jun 9, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

1

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

1

News mentions

1