# CVE-2026-77977: Ebyte NA111-M Missing Authentication for Critical Function

> Unauthenticated attackers on the adjacent network can reboot the device or restore factory settings, causing service disruption and configuration loss.

- **Severity:** High 7.2 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** 27 Aug 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-8g5x-wgwr-8jwp

## What is CVE-2026-77977?

CVE-2026-77977 is a high-severity missing authorization vulnerability in Ebyte NA111-M Firmware, published on 27 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Ebyte gateway product's vendor configuration utility does not require authentication before 
allowing certain disruptive administrative actions when default 
credentials remain configured. An unauthenticated attacker on the 
adjacent network could reboot the device or restore factory settings, 
resulting in a loss of configuration and service availability.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-77977 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-77977 is a high-severity missing authorization vulnerability in Ebyte NA111-M Firmware, published on 27 Aug 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-77977 in the wild and no public exploit code.

Affected product: Ebyte NA111-M Firmware. 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-77977/ (Markdown: https://insights.sbomify.com/CVE-2026-77977/index.md)
```

## Sources

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

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