dbcve.org
Tew 432brp FirmwareOperating system · Trendnet

CVE-2026-10062

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges 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 vulnerability was determined in TRENDnet TEW-432BRP 3.10B20. Affected by this vulnerability is the function formSetRoute of the file /goform/formSetRoute. This manipulation of the argument ip/mask/gateway causes stack-based buffer overflow. The attack is possible to be carried out remotely. The exploit has been publicly disclosed and may be utilized. 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 · moderate confidence

Stack-based buffer overflow vulnerability in TRENDnet TEW-432BRP router firmware (v3.10B20) in the formSetRoute function. The overflow is triggered via manipulation of ip/mask/gateway arguments passed to /goform/formSetRoute, allowing remote code execution.

MitigationNo vendor patch available as device is EOL since 2009. Replace affected device with a currently supported router model, or isolate the device behind a firewall with strict access controls to reduce attack surface.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Tew 432brp FirmwareOperating system
Affected:= 3.10b20

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 router model
    Check the device label or web interface login page for the model number TEW-432BRP
    Affected if The device is a TRENDnet TEW-432BRP router
  2. Check the firmware version
    Log into the router web interface (typically at 192.168.10.1) and navigate to the Status or System section to view the firmware version, or check the device label for firmware 3.10b20
    Affected if The firmware version is exactly 3.10b20
  3. Verify the web management interface is accessible
    Attempt to access the router's web interface on HTTP port 80 or HTTPS port 443 from the network segment you are checking
    Affected if The web management interface responds and accepts authentication
  4. Confirm remote management is enabled
    In the router web interface, check the Administration or Management settings for 'Enable Remote Management' or 'Web Management' access from WAN
    Affected if Remote management from WAN is enabled, making the interface externally accessible
  5. Test for formSetRoute parameter handling
    If you have authorized access, submit the formSetRoute (or Routing) configuration with ip/mask/gateway parameters exceeding normal length (e.g., ip=255.255.255.255 and additional characters)
    Affected if The router accepts oversized input without rejecting it or crashing

You are affected if you own a TEW-432BRP router running firmware 3.10b20 with the web management interface accessible from the network where the attacker resides.

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

No vendor patch available as device is EOL since 2009. Replace affected device with a currently supported router model, or isolate the device behind a firewall with strict access controls to reduce attack surface.

Recommended fix High confidence
  1. 1. Immediately isolate the affected TRENDnet TEW-432BRP device from untrusted networks or the public internet.
  2. 2. If the device's routing functionality is not required in your environment, disable it entirely.
  3. 3. Implement network segmentation to place the device in a restricted VLAN with limited access.
  4. 4. Deploy additional network monitoring to detect any exploitation attempts targeting the formSetRoute function.
  5. 5. Replace the EOL device with a currently supported router that receives security updates.
  6. 6. If the device must remain in service, restrict administrative access to a limited set of trusted IP addresses only.

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

Fix this in Tew 432brp Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10062 — 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-10062 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