CVE-2026-10122
Stack-Based Buffer Overflow in TRENDnet TEW-432BRP
Publication date: 2026-05-30
Last updated on: 2026-05-30
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| trendnet | tew-432brp | 3.10b20 |
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-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-10122 is a buffer overflow vulnerability found in the TRENDnet TEW-432BRP router, specifically in the function formSetProtocolFilter accessed via the /goform/formSetProtocolFilter endpoint.
The vulnerability occurs because the input parameter 'protocol_name' is copied directly to a local stack variable without proper validation or sanitization.
An attacker can exploit this by sending a specially crafted POST request with an excessively long string in the 'protocol_name' field, which overwrites the function's return address on the stack.
This leads to a stack-based buffer overflow, causing the router to crash and become unresponsive.
How can this vulnerability impact me? :
Exploitation of this vulnerability can cause the affected TRENDnet router to crash and stop providing network services, resulting in denial of service.
Since the buffer overflow allows overwriting of the return address, it may also potentially allow an attacker to execute arbitrary code, although the primary demonstrated impact is a crash.
Because the device is no longer supported and cannot be patched, the risk remains 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 specially crafted POST request to the '/goform/formSetProtocolFilter' endpoint with an excessively long string in the 'protocol_name' parameter. If the device is vulnerable, it will crash or become unresponsive.
A detection command example using curl would be:
- curl -X POST http://[router_ip]/goform/formSetProtocolFilter -d "protocol_name=$(python3 -c 'print("a"*1000)')"
If the router crashes or stops responding after this request, it indicates the presence of 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 no patches or fixes are available, immediate mitigation steps include:
- Isolate the vulnerable device from untrusted networks to prevent remote exploitation.
- Disable or restrict access to the '/goform/formSetProtocolFilter' endpoint if possible.
- Replace the device with a supported and updated router model to ensure security patches and support.