# CVE-2020-26913: Memory corruption in n/a

> Authenticated attackers can trigger a stack-based buffer overflow in NETGEAR router firmware to execute arbitrary code or escalate privileges.

- **Severity:** Medium 6.8 (`CVSS:3.1/AC:L/AV:A/A:H/C:H/I:H/PR:H/S:U/UI:N`)
- **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 Oct 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-qjcw-wqfm-p4vr

## What is CVE-2020-26913?

CVE-2020-26913 is a medium-severity memory corruption vulnerability in Netgear D6100 Firmware, published on 9 Oct 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Certain NETGEAR devices are affected by a stack-based buffer overflow by an authenticated user. This affects D6100 before 1.0.0.63, R7800 before 1.0.2.60, R8900 before 1.0.4.26, R9000 before 1.0.4.26, RBK20 before 2.3.0.28, RBR20 before 2.3.0.28, RBS20 before 2.3.0.28, RBK50 before 2.3.0.32, RBR50 before 2.3.0.32, RBS50 before 2.3.0.32, RBK40 before 2.3.0.28, RBR40 before 2.3.0.28, RBS40 before 2.3.0.28, SRK60 before 2.2.2.20, SRR60 before 2.2.2.20, SRS60 before 2.2.2.20, WN3000RPv2 before 1.0.0.78, WNDR4300v2 before 1.0.0.58, WNDR4500v3 before 1.0.0.58, WNR2000v5 before 1.0.0.70, XR450 before 2.3.2.40, and XR500 before 2.3.2.40.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2020-26913?

It affects 21 products.


Products: Netgear D6100 Firmware, Netgear R7800 Firmware, Netgear R8900 Firmware, Netgear R9000 Firmware, Netgear Rbk20 Firmware, Netgear Rbk40 Firmware, Netgear Rbk50 Firmware, Netgear Rbr20 Firmware, Netgear Rbr50 Firmware, Netgear Rbs20 Firmware, Netgear Rbs40 Firmware, Netgear Rbs50 Firmware, Netgear Srk60 Firmware, Netgear Srr60 Firmware, Netgear Srs60 Firmware, Netgear Wn3000rpv2 Firmware, Netgear Wndr4300v2 Firmware, Netgear Wndr4500v3 Firmware, Netgear Wnr2000v5 Firmware, Netgear Xr450 Firmware and 1 more.

## How do I fix CVE-2020-26913?

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

## Is CVE-2020-26913 being exploited?

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

## Other vulnerabilities in Netgear D6100 Firmware

- [CVE-2016-10174](https://insights.sbomify.com/CVE-2016-10174/): NETGEAR WNR2000v5 Router Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2018-21208](https://insights.sbomify.com/CVE-2018-21208/): Command injection in n/a (high 8.8)
- [CVE-2017-18764](https://insights.sbomify.com/CVE-2017-18764/): Command injection in n/a (high 8.8)
- [CVE-2018-21113](https://insights.sbomify.com/CVE-2018-21113/): Command injection in n/a (high 8.8)
- [CVE-2017-18776](https://insights.sbomify.com/CVE-2017-18776/): Auth bypass in n/a (high 8.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-26913 and fix it if it is affected.

What it is: CVE-2020-26913 is a medium-severity memory corruption vulnerability in Netgear D6100 Firmware, published on 9 Oct 2020. 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-2020-26913 in the wild and no public exploit code.

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

## Sources

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

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