A security flaw has been discovered in Tenda W20E 15.11.0.6(1068_1546_841)_CN_TDC. Impacted is the function formQOSRuleDel of the file /goform/delQos of the component QoS Rule Deletion. Performing a manipulation of the argument qosIndex results in stack-based buffer overflow. Remote exploitation of the attack is possible. The exploit has been released to the public and may be used for attacks.
Security readout for executives and security teams
Plain-English summary
Tenda W20E devices running the identified firmware contain a memory-corruption flaw in QoS rule deletion. An authenticated remote user may trigger a stack overflow through a crafted QoS index, potentially disrupting or compromising the device. The public sources do not identify a vendor-confirmed fix.
Executive priority
Prioritize immediate exposure reduction and vendor follow-up. Public exploit availability, low reported complexity, and potential complete security impact justify urgent action, especially for externally reachable management interfaces. Replacement should be considered if Tenda provides no timely supported fix.
Technical view
CVE-2026-19823 affects formQOSRuleDel at /goform/delQos in Tenda W20E firmware 15.11.0.6(1068_1546_841)_CN_TDC. Improper handling of qosIndex causes a stack-based buffer overflow, classified as CWE-119 and CWE-121. The CVSS v2 vector describes network access, low complexity, and required authentication.
Likely exposure
Exposure is established only for Tenda W20E devices running the exact listed firmware. Risk is greatest where the management endpoint is reachable by untrusted or compromised authenticated users. The supplied evidence does not establish that other firmware versions or Tenda products are affected.
Exploitation context
A public exploit or proof of concept is referenced, increasing practical risk. Remote exploitation is reported, although the CVSS vector indicates authentication is required. The CVE is not listed as KEV in the supplied bundle, and no cited evidence confirms active exploitation in the wild.
Researcher notes
The vulnerable data path is qosIndex processing by formQOSRuleDel. The supplied evidence does not establish exploit reliability, demonstrated code execution, vendor acknowledgement, a patched version, or active exploitation. Avoid extrapolating affected versions from the wildcard firmware CPE without additional vendor evidence.
Mitigation direction
Inventory Tenda W20E devices and identify those running the affected firmware.
Restrict device administration to trusted management networks and authorized users.
Check Tenda guidance and install a vendor-confirmed fixed firmware release when available.
If no fix exists, isolate or replace affected devices according to business risk.
Validation and detection
Confirm each device model and complete firmware build string.
Determine whether the management interface is reachable from untrusted networks.
Verify access controls prevent unauthorized users from reaching administrative endpoints.
Review device logs, unexpected reboots, and crashes associated with QoS administration.
Confirm remediation by recording the vendor-confirmed fixed firmware version after upgrading.
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.
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.
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: noTechnical 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.
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.
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.