# CVE-2026-73839: Ebyte NE2-D11 Insufficiently Protected Credentials

> Administrative credentials are exposed in plaintext in the management interface, allowing attackers to compromise device access.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:P/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:** 27 Aug 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-gv76-7x3r-m8gf

## What is CVE-2026-73839?

CVE-2026-73839 is a medium-severity vulnerability in Ebyte NE2-D11 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

Administrative credentials may be exposed in plaintext within the Ebyte 
device's management interface, increasing the risk of credential 
compromise through visual or remote observation. This undermines the 
confidentiality of device access.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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


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

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

## Is CVE-2026-73839 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-73839 is a medium-severity vulnerability in Ebyte NE2-D11 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-73839 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-73839/ (Markdown: https://insights.sbomify.com/CVE-2026-73839/index.md)
```

## Sources

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

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