# CVE-2026-75814: Ebyte NA111-M Cross-Site Request Forgery

> An attacker can trick an administrator into visiting a malicious page, leading to unauthorized configuration changes or device disruption on the Ebyte NA111-M.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-rrpm-rq88-pwc9

## What is CVE-2026-75814?

CVE-2026-75814 is a high-severity vulnerability in Ebyte NA111-M Firmware, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Ebyte device does not adequately verify the origin or authenticity of 
requests submitted to the web management interface. An unauthenticated 
remote attacker could persuade an authenticated administrator to visit a
 crafted page, causing unauthorized configuration changes or a 
disruption of device availability.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-75814 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-75814 is a high-severity vulnerability in Ebyte NA111-M Firmware, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-75814 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-75814/ (Markdown: https://insights.sbomify.com/CVE-2026-75814/index.md)
```

## Sources

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

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