dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2026-10183

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 vulnerability was identified in TRENDnet TEW-432BRP 3.10B20. This affects the function formWlanSetup of the file /goform/formWlanSetup. The manipulation of the argument enrollee leads to stack-based buffer overflow. The attack may be initiated remotely. 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 TRENDnet TEW-432BRP wireless router firmware version 3.10B20. The vulnerability is in the formWlanSetup function within /goform/formWlanSetup where the enrollee parameter is not properly bounds-checked before being copied to a stack-allocated buffer. This allows remote attackers to potentially execute arbitrary code via specially crafted HTTP requests.

MitigationSince the device is End-of-Life with no vendor patch available, immediately replace the vulnerable router with a currently supported model. If replacement is not immediately feasible, restrict network access to the device via firewall rules and isolate it from untrusted networks.

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 web interface or check the device label to confirm the model is TRENDnet TEW-432BRP
    Affected if Device is not a TRENDnet TEW-432BRP router, then it is not affected by this specific CVE
  2. Check the installed firmware version
    Log into the router web interface and navigate to the firmware version or status page, or check the label on the device for firmware version 3.10B20
    Affected if Firmware version is 3.10B20 (exact match to the affected version)
  3. Verify the vulnerable web interface is accessible
    Attempt to access http://[router-ip]/goform/formWlanSetup from a device on the same network. A response (even an error) indicates the interface is active
    Affected if The /goform/formWlanSetup endpoint responds to HTTP requests, meaning the vulnerable function is available
  4. Confirm wireless is enabled
    Log into the router web interface and check the wireless settings page to see if Wi-Fi is turned on
    Affected if Wireless is enabled, as the formWlanSetup function handles wireless configuration and is only active when wireless is configured

The device is affected if it is a TRENDnet TEW-432BRP router running firmware version 3.10B20, with the wireless feature enabled and the web interface accessible on the 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

Since the device is End-of-Life with no vendor patch available, immediately replace the vulnerable router with a currently supported model. If replacement is not immediately feasible, restrict network access to the device via firewall rules and isolate it from untrusted networks.

Recommended fix Low confidence
  1. This vulnerability affects TRENDnet TEW-432BRP firmware version 3.10B20, which has been End of Life (EOL) since 2009.
  2. The vendor has explicitly stated they cannot replicate or fix any vulnerabilities in this product as it has been EOL for 15+ years.
  3. No patch or firmware update is available from the vendor.
  4. Consider migrating to a supported, actively maintained router or network device.
  5. If continued use is required, place the device behind a firewall with restrictive ACLs to limit remote attack surface.
  6. Disable wireless management interfaces from untrusted networks if possible.
Caveat Device is End of Life with no vendor support; replacement with actively maintained hardware is recommended

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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