CVE-2026-8137: Totolink X5000R · Buffer Overflow
Affects Totolink X5000RSource CVE Database V5
Public exploit available · CVSS 8.7 High.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 8 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| TotolinkX5000R | Affected
| Fixed in– |
AI-suggested
Users should monitor Totolink's official channels for security advisories and updates addressing this vulnerability. Until a fix is released, limiting exposure of the affected device to untrusted networks and disabling remote management features, if possible, may reduce risk. Avoid using the vulnerable firmware version and plan to upgrade once a vendor-provided patch is available.
Description
CVE-2026-8137 is a high-severity buffer overflow vulnerability in the Totolink X5000R router firmware version 9.1.0u.6369_B20230113. The flaw exists in the function sub_458E40 within the /boafrm/formDdns file, where improper handling of the submit-url argument can lead to a buffer overflow condition. This vulnerability can be exploited remotely without user interaction and does not require privileges. Although the exploit code has been publicly disclosed, there are no confirmed reports of exploitation in the wild. No official patch or remediation guidance is currently available from the vendor. Users should monitor vendor advisories for updates and apply fixes once released.