# CVE-2026-2616: Beetel 777VR1 Web Management hard-coded credentials

> Attackers on the local network can use hard-coded credentials to access the Beetel 777VR1 web management interface.

- **Severity:** High 8.7 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Feb 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-cj49-hv2x-mxfw

## What is CVE-2026-2616?

CVE-2026-2616 is a high-severity vulnerability in Beetel 777VR1, published on 17 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability has been found in Beetel 777VR1 up to 01.00.09. The impacted element is an unknown function of the component Web Management Interface. The manipulation leads to hard-coded credentials. The attack needs to be initiated within the local network. The exploit has been disclosed to the public and may be used. It is advisable to modify the configuration settings. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-259 (Use of Hard-coded Password)

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

It affects 1 product.


Products: Beetel 777vr1 Firmware.

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

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

## Is CVE-2026-2616 being exploited?

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

## Other vulnerabilities in Beetel 777VR1

- [CVE-2026-2618](https://insights.sbomify.com/CVE-2026-2618/): Beetel 777VR1 SSH Service risky encryption (medium 6.3)
- [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-2616 and fix it if it is affected.

What it is: CVE-2026-2616 is a high-severity vulnerability in Beetel 777VR1, published on 17 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-2616 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-2616/ (Markdown: https://insights.sbomify.com/CVE-2026-2616/index.md)
```

## Sources

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

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