# CVE-2026-77975: Ebyte NA111-M Cleartext Storage of Sensitive Information

> An unauthenticated attacker on the adjacent network can recover administrative credentials from exported configuration files to access the device.

- **Severity:** High 7.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/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:** 31 Aug 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-mfqx-v89r-g539

## What is CVE-2026-77975?

CVE-2026-77975 is a high-severity vulnerability in Ebyte NE2-D11 Firmware, published on 31 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The affected Ebyte 

product exports administrative credentials and other 
sensitive configuration information without adequate protection. An 
unauthenticated attacker on the adjacent network who can obtain an 
exported configuration file could recover valid credentials and use them
 to access the device or similarly configured systems.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

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


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

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

## Is CVE-2026-77975 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-77975 is a high-severity vulnerability in Ebyte NE2-D11 Firmware, published on 31 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-77975 in the wild and no public exploit code.

Affected product: Ebyte NE2-D11 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-77975/ (Markdown: https://insights.sbomify.com/CVE-2026-77975/index.md)
```

## Sources

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

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