dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2026-10159

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 weakness has been identified in TRENDnet TEW-432BRP 3.10B20. Affected by this vulnerability is the function formSysLog of the file /goform/formSysLog. This manipulation of the argument current_page causes stack-based buffer overflow. The attack can be initiated remotely. The exploit has been made available to the public and could 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 confidence

Stack-based buffer overflow in TRENDnet TEW-432BRP's web interface function formSysLog allows remote attackers to overflow the current_page argument, potentially executing arbitrary code. The vulnerability exists in firmware version 3.10B20 and affects a publicly accessible HTTP service.

MitigationReplace the EOL device with a supported model; if immediate replacement is infeasible, isolate the device behind a firewall, disable WAN access, and restrict network exposure to prevent exploitation of this unpatchable flaw.

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. Confirm device model is TEW-432BRP
    Inspect the device physical label or access the web interface login page to identify the exact model number
    Affected if The device model is TRENDnet TEW-432BRP and the firmware has not been replaced with a non-vulnerable third-party firmware
  2. Determine if the web interface is network-accessible
    Attempt to access the web interface HTTP port (typically 80/tcp) from the network segment where the device is deployed
    Affected if The web interface responds to HTTP requests, indicating the vulnerable formSysLog function is exposed
  3. Check WAN/internet exposure of the web interface
    Review firewall rules, port forwarding configurations, or perform an external port scan to determine if TCP port 80 is reachable from the internet
    Affected if The device web interface is directly accessible from WAN/internet without NAT or firewall protection
  4. Verify network isolation status
    Examine network topology and ACLs to determine if the device is behind a properly configured internal network segment or DMZ
    Affected if The TEW-432BRP is not isolated behind a firewall or is directly accessible from untrusted network segments
  5. Look for signs of exploitation attempts
    Review device syslog or network traffic logs for unusual or excessively long POST requests to formSysLog or similar web endpoints
    Affected if Logs show anomalous requests containing unusually long strings in parameters that could indicate buffer overflow probing

A user is affected if they have a TRENDnet TEW-432BRP device with its web interface accessible from a network where untrusted parties can send HTTP requests directly to the device.

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

Replace the EOL device with a supported model; if immediate replacement is infeasible, isolate the device behind a firewall, disable WAN access, and restrict network exposure to prevent exploitation of this unpatchable flaw.

Recommended fix High confidence
  1. 1. Replace the EOL TRENDnet TEW-432BRP device with a currently supported router from TRENDnet or another vendor that provides security updates.
  2. 2. If immediate replacement is not possible, place the device in a restricted network segment (VLAN) to limit exposure to potential attackers.
  3. 3. Disable remote administration interfaces if not required, restricting management to trusted local networks only.
  4. 4. Monitor network traffic for signs of exploitation attempts targeting the /goform/formSysLog endpoint.
  5. 5. Implement external firewall rules to block unauthorized access to port 80/443 on the affected device if feasible.
Caveat This device is end-of-life with no vendor support; the only complete remediation is physical replacement with a currently-supported device.

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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