# CVE-2026-62658: Post-authentication Command Injection Vulnerability in certain Nighthawk RAX series models

> Authenticated attackers can execute arbitrary commands on NETGEAR Nighthawk RAX series routers, potentially compromising the device.

- **Severity:** Medium 4.7 (`CVSS:4.0/AV:A/AC:L/AT:P/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P`)
- **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:** 14 Jul 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-fj97-xjm9-5vjr

## What is CVE-2026-62658?

CVE-2026-62658 is a medium-severity command injection vulnerability in NETGEAR RAX43, published on 14 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A security flaw was discovered in certain NETGEAR Nighthawk RAX series routers
that could allow someone already logged in to the device to run unauthorized commands
or code on the router.

Weakness: CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2026-62658 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-62658 is a medium-severity command injection vulnerability in NETGEAR RAX43, published on 14 Jul 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-62658 in the wild and no public exploit code.

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

## Sources

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

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