Skip to main content

TRENDnet TEW-WLC100 EUVDEUVD-2026-60773

| CVE-2026-75784 CRITICAL
Stack-based Buffer Overflow (CWE-121)
2026-08-18 VulDB GHSA-xvh6-w8q3-q5g8
9.3
CVSS 4.0 · Vendor: VulDB
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach device HTTP management port
  2. Delivery
    Send crafted request with oversized Server header
  3. Exploit
    Overflow stack buffer in FUN_0040da4c
  4. Execution
    Corrupt return address / hijack control flow
  5. Persist
    Execute code or crash nginx
  6. Impact
    Compromise or disrupt controller

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Stack buffer bounds checking
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires network reachability to the TEW-WLC100's embedded nginx HTTP interface and the ability to send a crafted HTTP request that drives oversized attacker-controlled data into the 'Server' header handling path processed by FUN_0040da4c. Per the CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N), no authentication, no special attack requirement, and no user interaction are needed against the affected firmware. The principal limiting factor is exposure: the attacker must be able to route to the controller's web/management port, so devices confined to isolated management networks are far harder to reach. Confirmed affected scope is limited to firmware 1v2.07b01 on the TEW-WLC100; other builds or models are not established from the available data.

Impact

The signals mostly align toward elevated risk: the CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) describes a network-reachable, low-complexity, unauthenticated overflow with high impact to confidentiality, integrity, and availability, and the E:P exploit-maturity flag plus a linked GitHub POC confirm public exploit code exists. Countervailing factors temper the picture: this is a single-source VulDB disclosure with no NVD-authored CVSS 3.1 vector, no EPSS score, no CISA KEV listing, and no SSVC decision record provided, so several corroborating data points are simply missing rather than reassuring. No EPSS probability is available to gauge real-world exploitation likelihood, and the absence of KEV means there is no confirmation of active exploitation - the POC signals capability, not campaigns. The device itself is a niche wireless-LAN controller with a small deployment footprint, so mass internet-wide exploitation is less likely than targeted use against exposed management interfaces; any operator that exposes the controller's HTTP interface to untrusted networks should treat this as urgent and patch or isolate it promptly. Net assessment: a genuine high-severity, network-exploitable flaw whose real-world urgency depends heavily on whether the affected controllers are reachable from untrusted networks.

Exploit ScenarioDerived

An attacker who can reach the TEW-WLC100's HTTP management interface sends a crafted HTTP request whose Server-header-related input is oversized, overflowing the fixed stack buffer in FUN_0040da4c within the device's nginx binary. Given the low attack complexity and no authentication requirement (AC:L/PR:N/UI:N), a remote actor can trigger memory corruption to crash the service or attempt control-flow hijack for code execution. A public Python POC (poc-nginx-overflow.py) already demonstrates the overflow, lowering the barrier to reproduction.

Act Now Prioritize within 24-48h. Why: CRITICAL severity + public POC available.
1 public PoC No patch listed yet 1.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv2 – Aug 18, 2026

Remote stack-based buffer overflow in the embedded nginx binary (/usr/nginx/sbin/nginx) of the TRENDnet TEW-WLC100 wireless LAN controller, firmware 1v2.07b01, lets remote attackers overflow a fixed-size stack buffer in the HTTP Server-header handling routine FUN_0040da4c. Reported through VulDB with a public proof-of-concept exploit already available, the flaw carries a CVSS 4.0 base score of 9.3 and, per its vector, requires no authentication or user interaction. There is no public exploit identified as being used in active attacks - only a POC exists - but the combination of a network-reachable overflow and released exploit code makes this a high-priority patching candidate.

Earlier versions of this analysis (1)
v1 Aug 18, 2026 - 14:50 CVSS 10.0

Remote code execution in the TRENDnet TEW-WLC100 wireless LAN controller (firmware 1v2.07b01) stems from a stack-based buffer overflow in function FUN_0040da4c of the device's bundled nginx binary (/usr/nginx/sbin/nginx), reached by manipulating the HTTP 'Server' header handling. Unauthenticated attackers with network reach to the management web service can overflow the stack and gain full control of the appliance. Publicly available exploit code exists (a Python PoC published via VulDB researchers), and the CVSS 4.0 base score is a maximum 10.0, though there is no public exploit identified as being actively exploited in the wild (not in CISA KEV).

RemediationAI

No vendor-released patch or fixed firmware version is identified at time of analysis, and no TRENDnet advisory URL was provided in the source data, so the primary action is to monitor TRENDnet's support/security channels for a firmware update superseding 1v2.07b01 and apply it once released. In the interim, apply specific compensating controls: remove the TEW-WLC100 HTTP management interface from any untrusted or internet-facing network and restrict it to a dedicated management VLAN or jump host (trade-off: administrators must reach the controller through that restricted path); place an upstream filter or WAF/proxy that drops or normalizes anomalous or oversized HTTP request headers before they reach the device (trade-off: may not catch all overflow-triggering inputs and adds a hop); and enforce firewall ACLs limiting TCP access to the controller's web port to known administrator source addresses. Because a working POC is public (https://github.com/meishigana/CVE/blob/main/team15_20260702/02_wlc100-nginx/poc/poc-nginx-overflow.py), prioritize network isolation immediately rather than waiting for a patch. Do not treat absence of a published fix as confirmation that none will be released.

Affected VersionsENISA

TEW-WLC100 1v2.07b01

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The affected component is nginx, but not stock upstream nginx - it is TRENDnet's vendor-built binary shipped inside the TEW-WLC100 controller firmware, where reverse engineering identified the vulnerable routine as FUN_0040da4c (an unnamed function, consistent with analysis of a stripped embedded binary). The root cause is CWE-121 (stack-based buffer overflow): attacker-controllable input tied to the HTTP 'Server' header is copied into a fixed-size stack buffer without adequate bounds checking, corrupting the return address and adjacent stack data. On resource-constrained embedded appliances such overflows frequently lead to control-flow hijack because protections like stack canaries, ASLR, and non-executable stacks are often absent or weakened. The CPE cpe:2.3:a:trendnet:tew-wlc100 confirms the target is the TRENDnet TEW-WLC100 application/firmware stack rather than a general-purpose server.

Know when Tew Wlc100 gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulDB) PRIMARY 9.3 CRITICAL
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P
vuln.today AI 9.8 CRITICAL

Network-reachable, low-complexity, unauthenticated overflow with no user interaction; embedded nginx compromise plausibly yields full code execution, so C/I/A all High.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
High
Subsequent system: Integrity
High
Subsequent system: Availability
High

Lifecycle Timeline

2
CVSS changed
Aug 18, 2026 - 15:22 NVD
10.0 (CRITICAL) 9.3 (CRITICAL)
CVE Published
Aug 18, 2026 - 14:00 cve.org
CRITICAL 10.0

DescriptionCVE.org

A vulnerability was detected in TRENDnet TEW-WLC100 1v2.07b01. Affected by this issue is the function FUN_0040da4c of the file /usr/nginx/sbin/nginx of the component HTTP Header Handler. The manipulation of the argument Server results in stack-based buffer overflow. The attack may be launched remotely. The exploit is now public and may be used.

Latest POC

1 public PoC link from github

Sign in to open the public PoC links collected for this CVE.

Executive ViewAI

Why It Matters

The TRENDnet TEW-WLC100 wireless LAN controller (firmware 1v2.07b01) contains a critical remote code execution vulnerability that allows unauthenticated attackers to completely compromise wireless network infrastructure without requiring credentials or user interaction. With publicly available exploit code in circulation and no vendor patch available, this vulnerability presents an immediate and ongoing threat to organizational network security, access control, and data confidentiality. Any organization deploying this model must take urgent action to contain exposure.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: Restrict network access to the controller via firewall rules and IP whitelisting; implement network segmentation with the controller in a protected management VLAN; deploy intrusion detection/prevention rules targeting the HTTP Server-header buffer overflow pattern; establish continuous network monitoring and alerting for anomalous traffic to the TEW-WLC100 management interface; disable remote management access if operationally feasible and restrict all administrative access to console-only methods.

Threat Intelligence Overview

EPSS Score
1.0%
Top 39% exploitable
Prevalence
Low
niche TRENDnet SMB wireless LAN controller, limited enterprise footprint
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC Yes
EPSS 1.0%
Patch available No
Active threat No
Deciding rule
CRITICAL severity + public POC available
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Out-of-Cycle
Exploitation· derived
Poc
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
Very High

Priority Score

67
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +46
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

A stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it was allocated to hold.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy