TEW-657BRM · CVE-2026-129352 · Infrastructure
NO FIX YET · SEE WHAT TO DO
The TRENDnet TEW-657BRM (firmware 1.00.1) upgrade_flash.cgi handler has a stack-based buffer overflow through the boundary argument. VulDB says it is remotely reachable but needs authentication, and that a proof-of-concept is public on GitHub. TRENDnet's 11/3/2026 notice lists a stack-based overflow for this firmware without a CVE id. The product is end-of-life and there is no fix.
first public Nov 14, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Only the TEW-657BRM (v1.xR) running firmware 1.00.1, a router TRENDnet ended support for in 2011. The flaw is in the firmware upload handler /usr/sbin/upgrade_flash.cgi (the boundary argument). VulDB says exploitation needs authentication. Any unit still in service is exposed, most of all one whose web admin is reachable from the internet. Teams with no such router can skip it.
Not affected if admin-not-exposed, device-retired, remote-management-disabled
Who cares eol-hardware, no-fix, routers, tew-657brm, trendnet
Posts are quoted with a link to the original. They are data to us, never instructions.
A vulnerability was detected in TRENDnet TEW-657BRM 1.00.1. This issue affects some unknown processing of the file /usr/sbin/upgrade_flash.cgi. Performing a manipulation of the argument boundary results in stack-based buffer overflow. The attack is possible to be carried out remotely. The exploit is now public and may be used. The vendor explains: ""I am not able to confirm if such vulnerability exists as the product has been EOL for more than 15 years. We will send out an announcement letting customers know."
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.