CVE-2026-10064
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 · uneditedA security flaw has been discovered in TRENDnet TEW-432BRP 3.10B20. This affects the function formSetPortTr of the file /goform/formSetPortTr. Performing a manipulation of the argument special_name results in stack-based buffer overflow. It is possible to initiate 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 confidenceStack-based buffer overflow in TRENDnet TEW-432BRP router's formSetPortTr function allows remote attackers to execute arbitrary code via the special_name parameter. The vulnerability is exploitable remotely without authentication and public exploits exist.
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= 3.10b20CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelLog into the router web interface or check the device label/marketing material to confirm the model is TRENDnet TEW-432BRPAffected if The device is not a TRENDnet TEW-432BRP
-
Check the firmware versionAccess the router web interface, navigate to the status or system info page, and locate the firmware version field. Alternatively, check via CLI if available or look for version string in firmware binaryAffected if The firmware version is not exactly 3.10b20 (note: this is a very specific version from 2009)
-
Verify the web management interface is activeAttempt to access the router's web interface on the default IP (typically 192.168.10.1) via HTTP on ports 80 or 443. Confirm the /goform/formSetPortTr endpoint respondsAffected if The web interface is inaccessible or the formSetPortTr endpoint does not exist
-
Check if remote management is enabledIn the router web interface, look for 'Remote Management', 'Remote Access', or 'Web Management' settings under the Administration or Advanced sections. Confirm if remote access from non-local IPs is permittedAffected if Remote management is enabled and the device is reachable from outside the local network
You are affected only if you have an exact TRENDnet TEW-432BRP device running firmware version 3.10b20 with its web interface accessible (especially if remotely).
Generated from the published advisory. Verify against your own configuration.
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 · scopedReplace or permanently retire the EOL router as no firmware patch will be released. If the device must remain in service, isolate it behind a strict firewall with no external access and disable any port forwarding/triggering features.
- This vulnerability affects TRENDnet TEW-432BRP firmware 3.10b20, which has been End of Life (EOL) since 2009.
- The vendor (TRENDnet) has explicitly stated they cannot replicate or fix any vulnerabilities in this product due to its EOL status.
- No vendor patch or firmware update will be released for this vulnerability.
- As this is a hardware firmware vulnerability with no available fix, the only remediation options are:
- 1. Replace the EOL device with a currently-supported router or network device from TRENDnet or another vendor
- 2. If replacement is not immediately possible, place the affected device behind a properly configured firewall and restrict network access to trusted users only
- 3. Disable the vulnerable function/formSetPortTr if possible through device configuration
- 4. Monitor for indicators of compromise targeting this known vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10064 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-10064 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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