dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2026-10160

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 vulnerability has been detected in TRENDnet TEW-432BRP 3.10B20. Affected by this issue is the function formSetEnableWizard of the file /goform/formSetEnableWizard. Such manipulation of the argument start_wizard leads to stack-based buffer overflow. The attack can be launched remotely. The exploit has been disclosed publicly and may 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

Stack-based buffer overflow in TRENDnet TEW-432BRP firmware 3.10B20. The formSetEnableWizard handler fails to validate the length of the start_wizard parameter before copying it to a stack-allocated buffer, allowing remote attackers to overwrite stack memory and potentially execute arbitrary code.

MitigationNo vendor patch available (EOL product). Mitigations include: disable remote administration, isolate device behind NAT/firewall/network segmentation, or replace with a supported router.

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 router model
    Check the device label or access the admin interface to confirm the model is TRENDnet TEW-432BRP. This can be done by logging into the web management panel or physically inspecting the device.
    Affected if The device is a TRENDnet TEW-432BRP router
  2. Check the firmware version
    Access the router web interface, navigate to the System or Administration section, and locate the firmware version information. Compare it against version 3.10B20.
    Affected if The firmware version is 3.10B20 exactly (no other versions are listed as affected in this CVE)
  3. Verify web management interface accessibility
    Attempt to access the router login page at http://[router-ip] or check firewall rules to determine if the HTTP service (port 80) is listening on WAN/external interfaces.
    Affected if The router web interface is reachable from the network where remote attackers could send requests
  4. Confirm vulnerable endpoint exists
    Check if the /goform/formSetEnableWizard endpoint is present by reviewing firmware filesystem (if accessible via firmware extraction) or by observing responses from the device.
    Affected if The formSetEnableWizard endpoint is present and responds to requests containing the start_wizard parameter

You are affected if you have a TRENDnet TEW-432BRP router running firmware version 3.10B20 with the web management interface accessible to the network where untrusted users could send requests to /goform/formSetEnableWizard.

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 (EOL product). Mitigations include: disable remote administration, isolate device behind NAT/firewall/network segmentation, or replace with a supported router.

Recommended fix High confidence
  1. Replace the end-of-life TRENDnet TEW-432BRP router with a currently supported model from TRENDnet or another vendor.
  2. If immediate replacement is not possible, isolate the affected device on a restricted network segment to limit exposure.
  3. Consider implementing external firewall rules to block unauthorized access to the /goform/ endpoints.
  4. Monitor the device for any signs of exploitation and prepare for immediate retirement.
Caveat The affected hardware has reached end-of-life with no vendor support; replacement is the only remediation path.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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