# CVE-2026-2618: Beetel 777VR1 SSH Service risky encryption

> The Beetel 777VR1 router uses risky cryptographic algorithms in its SSH service, potentially allowing attackers to bypass security measures.

- **Severity:** Medium 6.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Feb 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-rfj2-v87v-5mg6

## What is CVE-2026-2618?

CVE-2026-2618 is a medium-severity vulnerability in Beetel 777VR1, published on 17 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm), CWE-310

## Which versions are affected by CVE-2026-2618?

It affects 1 product.


Products: Beetel 777vr1 Firmware.

## How do I fix CVE-2026-2618?

No fix has been published for CVE-2026-2618 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-2618 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-2618 exists.

## Other vulnerabilities in Beetel 777VR1

- [CVE-2026-2616](https://insights.sbomify.com/CVE-2026-2616/): Beetel 777VR1 Web Management hard-coded credentials (high 8.7)
- [CVE-2026-1410](https://insights.sbomify.com/CVE-2026-1410/): Beetel 777VR1 UART missing authentication (medium 5.4)
- [CVE-2026-1411](https://insights.sbomify.com/CVE-2026-1411/): Beetel 777VR1 UART access control (medium 5.4)
- [CVE-2020-36056](https://insights.sbomify.com/CVE-2020-36056/): Cross-site scripting in n/a (medium 5.4)
- [CVE-2026-2617](https://insights.sbomify.com/CVE-2026-2617/): Beetel 777VR1 Telnet Service/SSH Service insecure default initialization of resource (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-2618 and fix it if it is affected.

What it is: CVE-2026-2618 is a medium-severity vulnerability in Beetel 777VR1, published on 17 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-2618 exists.

Affected product: Beetel 777VR1. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-2618/ (Markdown: https://insights.sbomify.com/CVE-2026-2618/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-2618
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2618
- OSV: https://osv.dev/vulnerability/CVE-2026-2618

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-2618/
Summaries are generated and may contain mistakes; the official description above is the record.