CVE-2026-10160
Received Received - Intake
Stack-Based Buffer Overflow in TRENDnet TEW-432BRP

Publication date: 2026-05-31

Last updated on: 2026-05-31

Assigner: VulDB

Description
A security vulnerability has been detected in TRENDnet TEW-432BRP 3.10B20. Affected by this issue is the function formSetEnableWizard of the file /goform/formSetEnableWizard. Such manipulation of the argument start_wizard leads to stack-based buffer overflow. The attack can be launched remotely. The exploit has been disclosed publicly and may be used. The vendor explains: "This product has been EOL for 15 years (since 2009). As the item has been EOL for such a long time, we are not able to replicate or fix any vulnerabilities." This vulnerability only affects products that are no longer supported by the maintainer.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-31
Last Modified
2026-05-31
Generated
2026-05-31
AI Q&A
2026-05-31
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
trendnet tew-432brp 3.10b20
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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-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?

CVE-2026-10160 is a security vulnerability in the TRENDnet TEW-432BRP router, specifically in the function formSetEnableWizard accessed via the /goform/formSetEnableWizard endpoint.

The vulnerability is a stack-based buffer overflow caused by improper validation of user input. When a specially crafted long string is sent in a POST request, it overwrites the function's return address on the stack.

This leads to the router crashing and becoming unresponsive, disrupting its normal operation. The issue arises because input is copied directly into a local stack variable without proper sanitization.

The attack can be launched remotely, and a proof-of-concept has demonstrated how sending a long string (e.g., 837 'a' characters) triggers the crash.

The affected product has been end-of-life for 15 years and is no longer supported or patched by the vendor.


How can this vulnerability impact me? :

This vulnerability can cause the affected TRENDnet router to crash and become unresponsive, leading to denial of service.

Because the attack can be launched remotely, an attacker could disrupt network connectivity and availability by exploiting this buffer overflow.

Additionally, since the overflow overwrites the return address, it could potentially be exploited for arbitrary code execution, although this is not explicitly confirmed.

However, the device is no longer supported, so no fixes or patches are available, increasing the risk if the device is still in use.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by sending a crafted POST request with a long string (for example, 837 'a' characters) to the /goform/formSetEnableWizard endpoint on the affected TRENDnet TEW-432BRP router. If the device crashes or becomes unresponsive, it indicates the presence of the vulnerability.

A detection command example using curl would be:

  • curl -X POST -d "start_wizard=$(python3 -c 'print("a"*837)')" http://[router_ip]/goform/formSetEnableWizard

If the router stops responding or crashes after this request, it confirms the vulnerability.


What immediate steps should I take to mitigate this vulnerability?

Since the affected product TRENDnet TEW-432BRP has been end-of-life for 15 years and the vendor does not provide fixes or support, immediate mitigation steps include:

  • Discontinue use of the affected device and replace it with a supported and updated router model.
  • If replacement is not immediately possible, restrict network access to the device, especially blocking remote access to the /goform/formSetEnableWizard endpoint.
  • Implement network-level protections such as firewall rules to prevent unauthorized POST requests to the vulnerable endpoint.
  • Monitor the device for unusual crashes or unresponsiveness that may indicate exploitation attempts.

Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart