CVE-2026-24107: Tenda W20E · Code Injection
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 16:39 UTC
- EPSS
- 2.2% chance of exploitation in 30 days – higher than 82% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 2 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
To mitigate CVE-2026-24107, organizations should immediately check for firmware updates from Tenda addressing this vulnerability and apply them as soon as they become available. In the absence of official patches, users should disable any USB storage features on the router to reduce the attack surface. Network administrators should implement network segmentation to isolate vulnerable devices from critical infrastructure. Employing firewall rules to restrict access to the router’s management interfaces from untrusted networks can help prevent remote exploitation. Monitoring network traffic for unusual command execution patterns or unexpected outbound connections may detect exploitation attempts. Additionally, replacing vulnerable devices with models from vendors with robust security update policies should be considered for long-term risk reduction. Regularly auditing router configurations and disabling unused services further minimizes exposure.
Description
An issue was discovered in Tenda W20E V4.0br_V15.11.0.6. Failure to validate the value of `usbPartitionName`, which is directly used in `doSystemCmd`, may lead to critical command injection vulnerabilities.