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

CVE-2026-36803

CVE-2026-36803

Description

Tenda PW201A v1.0.5 has a buffer overflow in the qossetting function's 'page' parameter, allowing DoS via crafted HTTP requests.

AI Insight

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

Tenda PW201A v1.0.5 has a buffer overflow in the qossetting function's 'page' parameter, allowing DoS via crafted HTTP requests.

Vulnerability

A buffer overflow vulnerability exists in the qossetting function of Shenzhen Tenda Technology Co., Ltd Tenda PW201A v1.0.5, specifically within the handling of the page parameter. This function, identified by address 0x42e1c4 and registered via websFormDefine("qossetting",0x42e1c4), retrieves user-influenced HTTP parameters using websGetVar. The page parameter is then used in a sprintf command, leading to a buffer overflow when its value is excessively long [1].

Exploitation

An attacker can exploit this vulnerability by sending a crafted HTTP request to the qossetting CGI endpoint. The request must include a page parameter with a value significantly longer than expected, for example, a string of 888 or more characters. This requires the attacker to have network access to the device [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 device instability, rendering the device inoperable for legitimate users [1].

Mitigation

No patched version or specific mitigation details are available in the provided references. The vulnerability affects Tenda PW201A v1.0.5, which is noted as the latest version in one reference [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.