VulnerabilityPublished 25 Jan 2026Updated 23 Feb 2026

CVE-2026-1408: Beetel 777VR1 · Weak Password Requirements

Affects Beetel 777VR1Source CVE Database V5

Not known to be exploited · CVSS 1.0 Low.

Data as of 26 Oct 2026, 09: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 22% 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: 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.

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 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-1408, organizations should enforce strict physical security controls to prevent unauthorized access to Beetel 777VR1 devices, including locked server rooms, restricted access areas, and surveillance. Network segmentation should be employed to isolate critical devices and limit potential lateral movement if a device is compromised. Monitoring and logging physical access events can help detect suspicious activity. Since no patches are available, consider replacing affected devices with models from vendors that provide timely security updates. If replacement is not feasible, disable or restrict UART interface access where possible, or implement hardware-level protections to prevent unauthorized manipulation. Regularly audit device configurations and passwords to ensure compliance with strong security policies. Engage with the vendor for updates or consider third-party firmware solutions if available and secure. Finally, educate staff about the risks of physical device tampering and enforce policies to minimize exposure.

Description

A weakness has been identified in Beetel 777VR1 up to 01.00.09/01.00.09_55. This vulnerability affects unknown code of the component UART Interface. Executing a manipulation can lead to weak password requirements. The physical device can be targeted for the attack. The attack requires a high level of complexity. It is stated that the exploitability is difficult. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The primary impact of CVE-2026-1408 is the potential compromise of device security through weak password enforcement, which could allow unauthorized access to the Beetel 777VR1 device if an attacker gains physical access. This could lead to unauthorized configuration changes, network disruption, or further lateral movement within an affected network. However, the requirement for physical access and high attack complexity significantly reduces the risk of widespread exploitation. The vulnerability does not directly affect confidentiality, integrity, or availability over the network, limiting its scope. Organizations relying on these devices for critical network infrastructure could face localized security breaches if physical security controls are inadequate. The lack of vendor response and patches means that affected devices remain vulnerable, increasing long-term risk. Overall, the impact is low but non-negligible for environments where physical device security is weak or where the Beetel 777VR1 is deployed in sensitive or critical infrastructure.

Summary

CVE-2026-1408 identifies a security weakness in the Beetel 777VR1 device firmware versions 01.00.09 and 01.00.09_55, specifically within the UART interface component. The vulnerability manifests as weak password requirements, which can be manipulated by an attacker with physical access to the device. The UART interface is a hardware communication protocol often used for debugging or device management, and in this case, it exposes a mechanism that allows password manipulation. Exploiting this flaw requires a high level of technical skill and direct physical interaction with the device, limiting the attacker's reach. The vulnerability does not require authentication or user interaction, but the attack vector is constrained to physical proximity. The vendor, Beetel, was notified early but has not issued any response or patch, leaving the vulnerability unmitigated. The CVSS v4.0 score is 1.0, indicating a low severity due to the difficulty of exploitation and limited impact on confidentiality, integrity, and availability. No known exploits are currently active in the wild. This vulnerability primarily affects organizations deploying Beetel 777VR1 devices, which are typically used in networking contexts, potentially impacting device security and network integrity if exploited.

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