CVE-2026-2617: Beetel 777VR1 · Insecure Default Initialization of Resource
Affects Beetel 777VR1Source CVE Database V5
Public exploit available · CVSS 5.3 Medium.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 17 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Beetel777VR1 | Affected
| Fixed in– |
AI-suggested
Organizations should immediately restrict access to the Beetel 777VR1 devices by implementing strict network segmentation to isolate these routers from untrusted or guest networks. Disable Telnet and SSH services if not required, or restrict their access to trusted management hosts only. Employ strong network access controls such as MAC filtering and 802.1X authentication to limit local network access. Monitor network traffic for unusual activity targeting the router’s management interfaces. Maintain an inventory of affected devices and track vendor communications for future patches. Additionally, educate network administrators about the risk and ensure secure configuration management practices are followed.
Description
A vulnerability was found in Beetel 777VR1 up to 01.00.09. This affects an unknown function of the component Telnet Service/SSH Service. The manipulation results in insecure default initialization of resource. The attack can only be performed from the local network. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.