LiveActive security incident?Get immediate response
CVE Record

CVE-2026-75783: TRENDnet TEW-WLC100P DHCP blobmsg netifd stack-based overflow

A security vulnerability has been detected in TRENDnet TEW-WLC100P 12.07b01. Affected by this vulnerability is an unknown functionality of the file /sbin/netifd of the component DHCP blobmsg Handler. The manipulation leads to stack-based buffer overflow. The attack must be carried out from within the local network. The exploit has been disclosed publicly and may be used.

CriticalCVSS 9.6Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A nearby, unauthenticated attacker could target a vulnerable TRENDnet wireless controller through its DHCP handling. Successful exploitation may seriously affect data confidentiality, system integrity, and availability. The attack requires local-network access, limiting internet exposure but making compromised devices, guests, or insiders relevant threats.

Executive priority

Prioritize immediate identification and isolation of affected controllers. Local-network requirements reduce broad internet risk, but the critical impact and public exploit disclosure justify urgent action where untrusted or compromised devices can reach firmware 12.07b01.

Technical view

CVE-2026-75783 is a stack-based buffer overflow in the DHCP blobmsg handling of /sbin/netifd on TRENDnet TEW-WLC100P firmware 12.07b01. It has CVSS 3.1 score 9.6 with adjacent-network access, low complexity, no privileges, no user interaction, scope change, and high confidentiality, integrity, and availability impacts.

Likely exposure

Confirmed scope is limited to TRENDnet TEW-WLC100P firmware 12.07b01. Exploitation requires access from within an adjacent or local network. Exposure depends on whether untrusted, guest, or compromised devices can reach the controller's DHCP-related services.

Exploitation context

Public exploit material is referenced, so reproduction or abuse may be easier. However, the supplied sources do not establish active exploitation, and the CVE is not listed as CISA KEV. Treat the public disclosure as elevated risk, not evidence of attacks in the wild.

Researcher notes

The available description identifies the vulnerable binary and DHCP blobmsg component but does not explain the precise triggering condition or confirmed post-overflow outcome. No vendor patch or mitigation is named. Public proof-of-concept material exists; analyze it only in an authorized, isolated environment.

Mitigation direction

  • Inventory TEW-WLC100P controllers and identify devices running firmware 12.07b01.
  • Restrict controller access to trusted management and infrastructure networks.
  • Prevent guest and untrusted network segments from reaching affected DHCP-related services.
  • Check TRENDnet guidance for patched firmware or vendor-approved mitigations.
  • Increase monitoring for abnormal traffic, crashes, or restarts involving affected controllers.

Validation and detection

  • Confirm each controller's exact model and installed firmware version.
  • Review network paths from guest, user, and device segments to the controller.
  • Verify segmentation rules block unnecessary access to controller services.
  • Check logs and monitoring for unexplained netifd failures, crashes, or controller restarts.
  • Reassess after applying vendor guidance and document remaining reachable attack paths.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-119: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-121: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-75783 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H/E:P/RL:X/RC:R

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

4CVSS vectors
6Timeline events
1ADP providers
7Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total

CVSS vector scores

4 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.6CVSS 3.1CriticalCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H/E:P/RL:X/RC:R2.86VulDB
9.6CVSS 3.0CriticalCVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H/E:P/RL:X/RC:R2.86VulDB
9.4CVSS 4.0CriticalCVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P——VulDB
8.3CVSS 2.0HighAV:A/AC:L/Au:N/C:C/I:C/A:C/E:POC/RL:ND/RC:UR6.510VulDB

Vulnerability scoring details

Base CVSS 4.0 score

9.4Critical
CVSS 4.0 vector shape for CVE-2026-75783Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. Source timelineVulDB

    Advisory disclosed

  2. Source timelineVulDB

    VulDB entry created

  3. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  4. Source timelineVulDB

    VulDB entry last update

  5. CVE publishedCVE Program

    The CVE record was published.

  6. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
TRENDnetTEW-WLC100P12.07b01Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-119 · source CWE mapping

Improper Restriction of Operations within the Bounds of a Memory Buffer

Improper Restriction of Operations within the Bounds of a Memory Buffer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-121 · source CWE mapping

Stack-based Buffer Overflow

Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.