# CVE-2026-2702: Beetel 777VR1 WPA2 PSK hard-coded credentials

> Attackers with local network access can exploit hard-coded WPA2 PSK credentials to bypass security controls on Beetel 777VR1 routers.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Feb 2026
- **Updated:** 24 Feb 2026
- **Also known as:** GHSA-q6h4-vchv-83f2

## What is CVE-2026-2702?

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

### Official description

A security flaw has been discovered in Beetel 777VR1 up to 01.00.09. This issue affects some unknown processing of the component WPA2 PSK. Performing a manipulation results in hard-coded credentials. The attacker must have access to the local network to execute the attack. The complexity of an attack is rather high. The exploitability is assessed as difficult. The exploit has been released to the public and may be used for attacks. 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-2702?


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

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

## Is CVE-2026-2702 being exploited?

There is no known exploitation of CVE-2026-2702 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-2702 is a low-severity vulnerability in Beetel 777VR1, published on 19 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-2702 in the wild and no public exploit code.

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-2702/ (Markdown: https://insights.sbomify.com/CVE-2026-2702/index.md)
```

## Sources

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

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