# CVE-2026-62655: A DoS vulnerability due to stack overflow exists in certain NETGEAR Orbi models

> An unauthorized user can cause a stack overflow in NETGEAR Orbi devices, leading to device restarts and network disruption.

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

## What is CVE-2026-62655?

CVE-2026-62655 is a medium-severity denial of service vulnerability in NETGEAR RBE970, 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 found in certain NETGEAR Orbi models that
could allow an unauthorized user to cause the device to stop responding or
restart unexpectedly, disrupting network connectivity and making the device
temporarily unavailable.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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


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

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

## Is CVE-2026-62655 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-62655 is a medium-severity denial of service vulnerability in NETGEAR RBE970, 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-62655 in the wild and no public exploit code.

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

## Sources

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

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