VulnerabilityPublished 17 Feb 2026Updated 23 Feb 2026

CVE-2026-2618: Beetel 777VR1 · Risky Cryptographic Algorithm

Affects Beetel 777VR1Source CVE Database V5

Not known to be exploited · CVSS 6.3 Medium.

Data as of 26 Oct 2026, 09:16 UTC

CVSS 4.0 base score

6.3Medium

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

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

CVSS:4.0/AV:N/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: Network
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: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
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 17 Feb 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	Fixed in–

AI-suggested

Given the lack of vendor patches, organizations should implement compensating controls to mitigate CVE-2026-2618. These include restricting SSH access to trusted IP addresses via firewall rules or network segmentation to limit exposure to potential attackers. Employing VPNs or secure tunnels can add an additional encryption layer beyond the vulnerable SSH implementation. Monitoring SSH logs for unusual connection attempts or anomalies can help detect exploitation attempts early. Where possible, disable SSH services on Beetel 777VR1 devices if not strictly necessary, or replace devices with models that use up-to-date cryptographic algorithms and receive regular security updates. Network administrators should also consider using multi-factor authentication and strong key management practices to reduce the risk of credential compromise. Finally, organizations should maintain an inventory of affected devices and track any future vendor advisories or community-developed patches.

Description

A vulnerability was determined in Beetel 777VR1 up to 01.00.09. This impacts an unknown function of the component SSH Service. This manipulation causes risky cryptographic algorithm. The attack is possible to be carried out remotely. The attack is considered to have high complexity. The exploitability is said to be difficult. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The primary impact of CVE-2026-2618 is the potential weakening of SSH session security on affected Beetel 777VR1 devices. This could allow remote attackers to intercept or decrypt SSH communications, potentially exposing sensitive credentials or configuration data. While the vulnerability does not directly affect system integrity or availability, compromised SSH sessions could lead to further attacks if attackers gain administrative access. Organizations relying on Beetel 777VR1 for network connectivity or management may face increased risk of unauthorized access or data leakage. The high attack complexity and lack of known exploits reduce immediate risk, but the public disclosure and absence of vendor patches increase long-term exposure. This is particularly concerning for critical infrastructure or enterprise environments where secure remote management is essential. The inability to patch or mitigate the vulnerability through vendor support may force organizations to consider device replacement or additional network-level protections.

Summary

CVE-2026-2618 identifies a cryptographic weakness in the SSH Service component of the Beetel 777VR1 device, version 01.00.09 and earlier. The vulnerability arises from the use of a risky cryptographic algorithm, which may undermine the confidentiality and integrity of SSH sessions. The exact cryptographic function affected is unspecified, but the implication is that the algorithm does not meet current security standards, potentially allowing attackers to compromise encrypted communications. The vulnerability is remotely exploitable without requiring authentication or user interaction, but the attack complexity is high, indicating that a successful exploit would require significant skill or resources. The CVSS 4.0 base score is 6.3 (medium severity), reflecting limited impact on confidentiality and no impact on integrity or availability, with no privileges or user interaction needed. The vendor, Beetel, has not provided any patches or official response, leaving affected devices exposed. Although no active exploits have been observed in the wild, the public disclosure of the exploit details increases the risk of future attacks. This vulnerability highlights the importance of using strong, modern cryptographic algorithms in network services, especially those like SSH that protect sensitive administrative access.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Feb 2026, 13:43 UTC

Technical details

References

Community reviews

Related threats