VulnerabilityPublished 25 Jan 2026Updated 23 Feb 2026

CVE-2026-1409: Beetel 777VR1 · Improper Restriction of Excessive Authentication Attempts

Affects Beetel 777VR1Source CVE Database V5

Public exploit available · CVSS 1.0 Low.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score

1.0Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:P/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Physical
Attack Complexity: High
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable system. Physical interaction may be brief (e.g., evil maid attack) or persistent.
Attack Complexity: High: The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques, for example, circumvention of address space randomization (ASLR) or data execution prevention (DEP) must be performed for the attack to be successful; Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Jan 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Beetel777VR1	Affected =01.00.09 =01.00.09_55	Fixed in–

AI-suggested

To mitigate CVE-2026-1409, organizations should implement strict physical security controls to prevent unauthorized access to Beetel 777VR1 devices, including locked enclosures and restricted access areas. Network segmentation can limit exposure if devices are compromised. Monitoring physical device integrity and access logs can help detect tampering attempts. Since no patches are currently available, consider deploying additional authentication layers or external access controls to reduce reliance on the vulnerable UART interface. Regularly check for vendor updates or firmware patches addressing this issue. If possible, replace affected devices with models that have robust authentication protections and rate limiting on physical interfaces. Conduct security audits to identify devices with this firmware version and prioritize their protection accordingly.

Description

A security vulnerability has been detected in Beetel 777VR1 up to 01.00.09/01.00.09_55. This issue affects some unknown processing of the component UART Interface. The manipulation leads to improper restriction of excessive authentication attempts. It is possible to launch the attack on the physical device. The attack's complexity is rated as high. The exploitability is assessed as difficult. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The primary impact of CVE-2026-1409 is the potential for an attacker with physical access to the Beetel 777VR1 device to perform repeated authentication attempts without effective restriction, possibly enabling brute force attacks against authentication mechanisms. However, due to the high complexity and requirement for physical access, the likelihood of exploitation in typical organizational environments is low. Confidentiality, integrity, and availability impacts are minimal since the vulnerability does not directly allow remote compromise or privilege escalation. The absence of vendor response and patches means affected devices remain vulnerable, which could be a concern in high-security environments where physical device access cannot be fully controlled. Organizations relying on these devices for critical network functions may face increased risk if attackers can physically access the hardware, potentially leading to unauthorized access or device manipulation.

Summary

CVE-2026-1409 identifies a security vulnerability in the Beetel 777VR1 device firmware versions 01.00.09 and 01.00.09_55. The issue arises from improper restriction of excessive authentication attempts processed through the UART interface component. This flaw allows an attacker with physical access to the device to attempt multiple authentication tries without effective rate limiting or lockout mechanisms. The attack complexity is high, indicating that exploitation requires specialized knowledge or conditions, and the exploitability is difficult. The vulnerability does not require any privileges, user interaction, or network access, as it targets the physical UART interface directly. The CVSS 4.0 base score is 1.0, reflecting low severity due to limited impact on confidentiality, integrity, and availability, and the lack of remote exploitability. The vendor was notified but has not issued patches or responses, and no known exploits have been observed in the wild. This vulnerability could potentially be leveraged to bypass authentication controls if an attacker gains physical access, but the practical risk remains low given the complexity and access requirements.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 22:24 UTC

Technical details

References

Community reviews

Related threats