Skip to main content
Menu
CVEs

TRENDnet TEW-657BRM remote memory corruption in mini_httpd

CVE-2026-129351EUVD-2026-125948GHSA-R63Q-P323-QRRFPublished November 14, 2026, updated

10.0CriticalCNA
Exploited
Proof of concept public, per CISA
Fix
No fix listed
Who is exposed
Not reported

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.

Written by a model

Original 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 systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

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-18):
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"}.

Affected versions

cve.now Index

50of 100 · methodology v3
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 10.0, total technical impact per CISA
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 80 if added to CISA KEV
  • Would score about 75 if CISA's SSVC rates exploitation active
  • Would score about 55 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now4 days
  4. CISA SSVC assessment

    Exploitation: poc · Automatable: yes · Technical impact: total

  5. Record last updated

Public exploit activity

10Posted on X by cve.now100%0Nov 14Nov 22
  • GitHub PoC repos: 1
  • EPSS: 0.84%
  • Posted on X by cve.now Nov 14

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

On X 1

Evidence 8

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-129351
RecordNVD · CVE-2026-129351
Public exploit code 2Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
ExploitGitHub · ruanyi101/router-firmware-security-advisories · Advisory TRENDnet-TEW-657BRM-mini_httpd.md
ExploitGitHub · googlesky/CVE-2026-129351 · Repository
Other links 4
AdvisoryVulDB · Advisory #437397
AdvisoryVulDB · Threat intelligence #437397
AdvisoryVulDB · CVE-2026-129351 record
AdvisoryVulDB · Submission #1043518

Questions about CVE-2026-129351

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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-129351?

TEW-657BRM: version 1.00.1.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.