CVE-2026-10181
Stack-Based Buffer Overflow in TRENDnet TEW-432BRP
Publication date: 2026-05-31
Last updated on: 2026-05-31
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-10181 is a stack-based buffer overflow vulnerability found in the TRENDnet TEW-432BRP router. It occurs in the function formSysCmd at the /goform/formSysCmd endpoint, specifically when handling the submit-url parameter. The vulnerability arises because the input for submit-url is copied directly into a stack-based local variable without proper validation, allowing an attacker to overwrite the function's return address.
An attacker can exploit this vulnerability remotely by sending a crafted HTTP POST request with an excessively long submit-url value. This causes the router to crash and become unresponsive, effectively denying service.
The affected product has been end-of-life for 15 years, and the vendor does not provide fixes or support for this vulnerability.
How can this vulnerability impact me? :
This vulnerability can impact you by allowing a remote attacker to cause a denial of service on the affected TRENDnet TEW-432BRP router. By exploiting the buffer overflow, the attacker can crash the device, making it unresponsive and unable to provide network services.
Since the device becomes inoperable after the attack, it can disrupt network connectivity and potentially affect any systems relying on this router for internet or intranet access.
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 HTTP POST request to the /goform/formSysCmd endpoint with an excessively long submit-url parameter. If the device crashes or becomes unresponsive, it indicates the presence of the vulnerability.
A simple detection command using curl could be:
- curl -X POST http://<target-ip>/goform/formSysCmd -d "submit-url=$(python3 -c 'print("a"*1000)')"
If the device crashes or stops responding after this request, it is vulnerable to the stack-based buffer overflow.
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 are available, immediate mitigation steps include:
- Isolate the vulnerable device from untrusted networks to prevent remote exploitation.
- Disable or restrict access to the /goform/formSysCmd endpoint if possible.
- Monitor network traffic for suspicious POST requests with unusually long submit-url parameters.
- Consider replacing the device with a supported and updated model to ensure security.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify any direct impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.