dbcve.org
Tew 432brp FirmwareOperating system · Trendnet

CVE-2026-10063

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 identified in TRENDnet TEW-432BRP 3.10B20. Affected by this issue is the function formWPS of the file /goform/formWPS. Such manipulation of the argument peerPin leads to stack-based buffer overflow. The attack may be performed from remote. The exploit is publicly available and might be used. 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 TRENDnet TEW-432BRP wireless router's web interface (formWPS function in /goform/formWPS). The overflow occurs when handling the peerPin argument, allowing remote attackers to potentially execute arbitrary code. This is a critical flaw as it is remotely exploitable and a public exploit exists.

MitigationSince the vendor will not provide a patch (EOL product), the device should be isolated from untrusted networks or replaced with a supported device. If the WPS feature cannot be disabled, network segmentation and strict firewall rules should be applied to limit exposure.

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 device model
    Locate the router label or access the web administration interface to confirm the model number is TRENDnet TEW-432BRP
    Affected if The device is a TRENDnet TEW-432BRP
  2. Check the firmware version
    Access the router web interface (typically at 192.168.10.1) and navigate to the Status or Firmware Upgrade page to view the installed firmware version
    Affected if The firmware version is 3.10b20
  3. Verify WPS is enabled
    Access the router web interface and check the WPS (Wi-Fi Protected Setup) settings page to determine if WPS functionality is currently enabled
    Affected if WPS is enabled on the device
  4. Confirm formWPS accessibility
    Attempt to access the formWPS endpoint via HTTP POST to the router's web interface, or verify the WPS configuration page is reachable from the network
    Affected if The WPS configuration interface is accessible on the network

The device is affected if it is a TRENDnet TEW-432BRP running firmware version 3.10b20 with WPS functionality enabled and accessible.

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

Since the vendor will not provide a patch (EOL product), the device should be isolated from untrusted networks or replaced with a supported device. If the WPS feature cannot be disabled, network segmentation and strict firewall rules should be applied to limit exposure.

Recommended fix High confidence
  1. 1. Isolate the affected TRENDnet TEW-432BRP router on a restricted network segment to limit remote attack surface.
  2. 2. If WPS functionality is accessible via the router's web interface, attempt to disable it under Wireless Settings > WPS.
  3. 3. Implement strict firewall rules to block external access to the router's management interface (ports 80/443).
  4. 4. Monitor network traffic for any signs of exploitation attempts targeting the /goform/formWPS endpoint.
  5. 5. Replace the EOL device with a currently supported router that receives security updates.
Caveat No upgrade path available - TRENDnet TEW-432BRP has been End of Life since 2009 and is no longer supported by the vendor; device replacement is the only viable remediation.

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

Fix this in Tew 432brp Firmware 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-10063 — 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-10063 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