Skip to main content
Menu
CVEs

TRENDnet TEW-657BRM unauthenticated information disclosure in mini_httpd

CVE-2026-133492EUVD-2026-131075GHSA-C7P5-RF76-XJC9Published November 20, 2026, updated

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

Summary

TRENDnet TEW-657BRM has a flaw in its mini_httpd component that lets an attacker obtain information the device should not expose. The flaw can be reached remotely over the network, without logging in.

Written by a model

Original description

A vulnerability has been found in TRENDnet TEW-657BRM 1.00.1. The impacted element is an unknown function of the file /usr/www/images/.svn/entries of the component mini_httpd. The manipulation leads to information disclosure. It is possible to initiate the attack remotely. The exploit has been disclosed to the 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 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-133492 (TRENDnet TEW-657BRM mini_httpd entries information disclosure), 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-133492 (entry last updated 2026-11-20):
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-133492 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133492 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/440910
- https://vuldb.com/vuln/440910/cti
- https://vuldb.com/cve/CVE-2026-133492
- https://vuldb.com/submit/1049873
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-133492
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-133492"}.

Affected versions

cve.now Index

47Pof 100 · provisional · 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
  • Severity6.9/10CVSS 6.9
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 77 if added to CISA KEV
  • Would score about 72 if CISA's SSVC rates exploitation active
  • Would score about 52 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

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

  4. Record last updated

Evidence 7

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

Questions about CVE-2026-133492

Is CVE-2026-133492 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-133492?

TEW-657BRM: version 1.00.1.

Source: cve.now feed data

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