# CVE-2026-1411: Beetel 777VR1 UART access control

> Attackers with physical access can bypass UART access controls on Beetel 777VR1 devices to gain elevated privileges or execute code.

- **Severity:** Medium 5.4 (`CVSS:4.0/AV:P/AC:H/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jan 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-5vmx-5g6g-mcfc

## What is CVE-2026-1411?

CVE-2026-1411 is a medium-severity authentication bypass vulnerability in Beetel 777VR1, published on 26 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw has been found in Beetel 777VR1 up to 01.00.09/01.00.09_55. The affected element is an unknown function of the component UART Interface. This manipulation causes improper access controls. It is feasible to perform the attack on the physical device. The complexity of an attack is rather high. The exploitability is described as difficult. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-284 (Improper Access Control), CWE-266 (Incorrect Privilege Assignment)

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

It affects 1 product.


Products: Beetel 777vr1 Firmware.

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

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

## Is CVE-2026-1411 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1411 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-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-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-1411 and fix it if it is affected.

What it is: CVE-2026-1411 is a medium-severity authentication bypass vulnerability in Beetel 777VR1, published on 26 Jan 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-1411 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-1411/ (Markdown: https://insights.sbomify.com/CVE-2026-1411/index.md)
```

## Sources

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

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