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

CVE-2026-36794

CVE-2026-36794

Description

Tenda W3 Wireless Router v1.0.0.3(2204) has stack overflows in R7WebsSecurityHandler via username/password, allowing DoS and potential RCE.

AI Insight

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

Tenda W3 Wireless Router v1.0.0.3(2204) has stack overflows in R7WebsSecurityHandler via username/password, allowing DoS and potential RCE.

Vulnerability

Shenzhen Tenda Technology Co., Ltd Tenda W3 Wireless Router v1.0.0.3(2204) contains stack-based buffer overflow vulnerabilities in the R7WebsSecurityHandler CGI handler. These vulnerabilities are reachable via the username and password parameters in HTTP requests, provided both parameters are non-null. The strcpy function is used to copy the username without length validation, leading to overwrites of adjacent stack memory [1].

Exploitation

An attacker can exploit this vulnerability by sending a crafted HTTP request to the R7WebsSecurityHandler CGI endpoint. The request must include non-null password and an overly long username parameter. The vulnerability is reachable during normal operation as a session slot is typically available [1].

Impact

Successful exploitation of these vulnerabilities can lead to a Denial of Service (DoS) by causing the device to crash or reboot. The references also suggest the potential for arbitrary code execution, though this is not detailed [1].

Mitigation

No patched version or specific mitigation details are available in the provided references. The vulnerability affects Tenda W3 Wireless Router v1.0.0.3(2204) [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

0

No linked articles in our index yet.