# CVE-2026-76179: Ebyte NA111-M Use of GET Request Method With Sensitive Query Strings

> Attackers can steal authentication tokens from exposed session data to impersonate users and gain unauthorized access to Ebyte gateway management interfaces.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-62mm-rmvp-f5p7

## What is CVE-2026-76179?

CVE-2026-76179 is a critical vulnerability in Ebyte NA111-M Firmware, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An improper protection of authentication tokens vulnerability exists in 
certain Ebyte gateway products. Authentication tokens used by the web 
management interface are insufficiently protected during client-side 
session handling, which may allow an attacker with access to exposed 
session information to obtain and reuse a valid token. Successful 
exploitation could allow an attacker to impersonate an authenticated 
user and gain unauthorized access to device management functionality.

Weakness: CWE-598 (Use of HTTP Request With Sensitive Query String)

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


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

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

## Is CVE-2026-76179 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76179 is a critical vulnerability in Ebyte NA111-M Firmware, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-76179 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-76179/ (Markdown: https://insights.sbomify.com/CVE-2026-76179/index.md)
```

## Sources

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

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