dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2026-10158

HIGH · 8.8 CVSS v3.1 Published 2026-05-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A stack-based buffer overflow vulnerability exists in the formPortFw function of TRENDnet TEW-432BRP firmware 3.10B20. The server_name parameter is not properly validated before being used in a stack-allocated buffer, allowing remote attackers to overwrite return addresses and potentially execute arbitrary code.

MitigationReplace the end-of-life TEW-432BRP with a currently supported router; if replacement is not immediately feasible, isolate the device behind a firewall and disable WAN management access to reduce exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the router's web interface (typically on port 80) and check the login page or admin section for the model name 'TEW-432BRP' or check the HTTP server banner using a tool like nmap or curl -I against the router's IP
    Affected if The device is a TRENDnet TEW-432BRP router
  2. Verify the vulnerable endpoint exists
    Send an HTTP GET request to http://[ROUTER_IP]/goform/formPortFw and check if the endpoint responds (even with an error)
    Affected if The endpoint /goform/formPortFw is accessible and responds
  3. Confirm web interface is network-accessible
    Check if HTTP port 80 (or HTTPS if configured) is open on the router's IP address using nmap -p 80 [ROUTER_IP] or telnet/netcat
    Affected if The router's web interface is exposed on the network (not isolated)
  4. Check for firmware version information
    Log into the router admin panel and look for a 'System' or 'Status' page that displays the firmware version, or check the HTTP response headers for version information
    Affected if Firmware version cannot be determined or is confirmed as an older unreleased version from 2009 era

A user is affected if a TRENDnet TEW-432BRP router with an accessible /goform/formPortFw web interface is present on their network

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace the end-of-life TEW-432BRP with a currently supported router; if replacement is not immediately feasible, isolate the device behind a firewall and disable WAN management access to reduce exposure.

Recommended fix High confidence
  1. Replace the affected TRENDnet TEW-432BRP router with a currently supported model from TRENDnet or another vendor.
  2. If immediate replacement is not possible, place the device behind a properly configured firewall with strict inbound access control rules to limit exposure to remote attacks.
  3. Disable remote management interfaces on the router if not strictly necessary.
  4. Monitor network traffic for suspicious patterns targeting the /goform/formPortFw endpoint.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10158 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-10158 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data