# CVE-2026-0417: Insufficient input validation in certain NETGEAR routers

> Authenticated local administrators can tamper with router integrity due to insufficient input validation in NETGEAR devices.

- **Severity:** Medium 4.3 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:U/V:D/RE:L/U:Amber`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jun 2026
- **Updated:** 10 Jun 2026
- **Also known as:** GHSA-gp45-6q59-r2fj

## What is CVE-2026-0417?

CVE-2026-0417 is a medium-severity vulnerability in Netgear R6900p Firmware, published on 9 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Insufficient input validation vulnerability in the listed NETGEAR devices allows
authenticated administrators connected to the local network to tamper with
the router's integrity.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 27 products.


Products: Netgear Mr60 Firmware, Netgear Mr70 Firmware, Netgear Mr80 Firmware, Netgear Ms60 Firmware, Netgear Ms70 Firmware, Netgear Ms80 Firmware, Netgear R6400v2 Firmware, Netgear R6700v3 Firmware, Netgear R6900p Firmware, Netgear R7000 Firmware, Netgear R7000p Firmware, Netgear R7960p Firmware, Netgear R8000p Firmware, Netgear R8500 Firmware, Netgear Rax20 Firmware, Netgear Rax35v2 Firmware, Netgear Rax40v2 Firmware, Netgear Rax41 Firmware, Netgear Rax42 Firmware, Netgear Rax43 Firmware and 7 more.

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

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

## Is CVE-2026-0417 being exploited?

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

## Other vulnerabilities in Netgear R6900p Firmware

- [CVE-2022-48322](https://insights.sbomify.com/CVE-2022-48322/): Memory corruption in n/a (critical 9.8)
- [CVE-2021-45539](https://insights.sbomify.com/CVE-2021-45539/): Command injection in n/a (high 8.4)
- [CVE-2021-45540](https://insights.sbomify.com/CVE-2021-45540/): Command injection in n/a (high 8.4)
- [CVE-2021-45541](https://insights.sbomify.com/CVE-2021-45541/): Command injection in n/a (high 8.4)
- [CVE-2022-48176](https://insights.sbomify.com/CVE-2022-48176/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-0417 is a medium-severity vulnerability in Netgear R6900p Firmware, published on 9 Jun 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-0417 in the wild and no public exploit code.

Affected product: Netgear R6900p 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-0417/ (Markdown: https://insights.sbomify.com/CVE-2026-0417/index.md)
```

## Sources

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

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