CVE-2026-10064
Awaiting Analysis Awaiting Analysis - Queue
Stack-Based Buffer Overflow in TRENDnet TEW-432BRP

Publication date: 2026-05-29

Last updated on: 2026-05-29

Assigner: VulDB

Description
A security flaw has been discovered in TRENDnet TEW-432BRP 3.10B20. This affects the function formSetPortTr of the file /goform/formSetPortTr. Performing a manipulation of the argument special_name results in stack-based buffer overflow. It is possible to initiate the attack remotely. The exploit has been released to the public and may be used for attacks. 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-29
Last Modified
2026-05-29
Generated
2026-05-29
AI Q&A
2026-05-29
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
trendnet tew-432brp to 2009 (exc)
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-10064 is a security vulnerability in the TRENDnet TEW-432BRP device, specifically in the function formSetPortTr accessed via the /goform/formSetPortTr endpoint.

The vulnerability arises because the input parameter 'special_name' is copied directly to a local stack variable without proper validation, leading to a stack-based buffer overflow.

An attacker can exploit this by sending a specially crafted POST request with an excessively long 'special_name' value, which overwrites the function's return address and causes the device to crash or become unresponsive.

This flaw can be triggered remotely and the exploit code has been publicly released.


How can this vulnerability impact me? :

Exploiting this vulnerability can cause the affected TRENDnet device to crash and become unresponsive, disrupting its normal operation and network services.

This denial of service can lead to loss of connectivity or interruption of network functions relying on the device.

Additionally, because the buffer overflow overwrites the return address, it may potentially allow an attacker to execute arbitrary code, leading to further compromise of the device.

However, this vulnerability only affects devices that have been end-of-life for over 15 years and are no longer supported or patched by the vendor.


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/formSetPortTr' endpoint with an excessively long 'special_name' parameter. 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 "special_name=$(python3 -c 'print("a"*1000)')" http://<target-ip>/goform/formSetPortTr

If the device stops responding or crashes after this request, it is vulnerable to CVE-2026-10064.


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 remote management or restrict access to the device's management interface.
  • Replace the device with a supported and updated model to ensure ongoing security.

These steps help reduce the risk of exploitation given the lack of vendor support or patches.


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