CVE-2026-10158
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 flaw has been discovered in TRENDnet TEW-432BRP 3.10B20. Affected is the function formPortFw of the file /goform/formPortFw. The manipulation of the argument server_name results in stack-based buffer overflow. It is possible to launch 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-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-10158 is a security vulnerability in the TRENDnet TEW-432BRP router, specifically in the formPortFw function of the /goform/formPortFw file. The vulnerability arises because the server_name parameter in an HTTP POST request is copied into a stack-based local variable without proper input validation.

This lack of validation allows an attacker to send an excessively long server_name value, causing a stack-based buffer overflow. This overflow can overwrite the function's return address, leading to a crash or disruption of the router's normal operation.

The attack can be launched remotely, and a proof-of-concept exploit has been publicly released.


How can this vulnerability impact me? :

This vulnerability can cause the affected TRENDnet router to crash or stop functioning properly when exploited, resulting in a denial of service.

Since the exploit can be launched remotely, an attacker could disrupt your network connectivity by targeting the router.

Because the product has been end-of-life for 15 years and is no longer supported, there are no fixes or patches 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 an HTTP POST request to the endpoint /goform/formPortFw with an excessively long server_name parameter. If the device is vulnerable, it will crash or stop functioning properly due to a stack-based buffer overflow.

A simple detection method is to send a long string of characters (for example, a string of 'a' characters) as the server_name value in the POST request and observe if the router crashes or becomes unresponsive.

Example command using curl to test the vulnerability:

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

Replace [router_ip] with the IP address of the TRENDnet TEW-432BRP device. If the device crashes or stops responding after this request, it is likely vulnerable.


What immediate steps should I take to mitigate this vulnerability?

Since the affected product TRENDnet TEW-432BRP has been end-of-life (EOL) for 15 years and the vendor does not provide patches or fixes, immediate mitigation steps are limited.

  • Remove or isolate the vulnerable device from the network to prevent remote exploitation.
  • Disable remote management or restrict access to the device's management interface to trusted internal networks only.
  • Consider replacing the device with a currently supported and patched model to ensure ongoing 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.


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