Beetel 777VR1 WPA2 PSK hard-coded credentials
Key facts
- Attack vector
- Adjacent network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- High
- Attack requirements
- None
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- Low · None · None
- Fix status
- No fix listed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-259.
Summary
A security flaw has been discovered in Beetel 777VR1 up to 01.00.09. This issue affects some unknown processing of the component WPA2 PSK. Performing a manipulation results in hard-coded credentials. The attacker must have access to the local network to execute the attack. The complexity of an attack is rather high. The exploitability is assessed as difficult. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2026-2702
- 2026-10-03 Alias added: GHSA-q6h4-vchv-83f2
References
More Beetel vulnerabilities
- TI-2026-02232 Beetel 777VR1 Web Management hard-coded credentials CVSS 4.0HIGH 8.7
- TI-2026-02234 Beetel 777VR1 SSH Service risky encryption CVSS 4.0MEDIUM 6.3
- TI-2026-01109 Beetel 777VR1 UART access control CVSS 4.0MEDIUM 5.4
- TI-2026-01108 Beetel 777VR1 UART missing authentication CVSS 4.0MEDIUM 5.4
- TI-2026-56880 Beetel 450TC3 password recovery CVSS 4.0MEDIUM 5.3
- TI-2026-02233 Beetel 777VR1 Telnet Service/SSH Service insecure default initialization of resource CVSS 4.0MEDIUM 5.3
Sources
- CVE-2026-2702 · CVE Program
- CVE-2026-2702 · NVD
- FIRST EPSS
- GHSA-q6h4-vchv-83f2 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences