# CVE-2020-26920: Command injection in n/a

> Unauthenticated attackers can execute arbitrary commands on NETGEAR Orbi devices via command injection vulnerabilities.

- **Severity:** High 8.8 (`CVSS:3.1/AC:L/AV:A/A:H/C:H/I:H/PR:N/S:U/UI:N`)
- **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:** 9 Oct 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-376w-gx8h-h6vg

## What is CVE-2020-26920?

CVE-2020-26920 is a high-severity command injection vulnerability in n/a, 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 command injection by an unauthenticated attacker. This affects SRK60 before 2.5.3.110, SRR60 before 2.5.3.110, and SRS60 before 2.5.3.110.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

It affects 3 products.


Products: Netgear Srk60 Firmware, Netgear Srr60 Firmware, Netgear Srs60 Firmware.

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

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

## Is CVE-2020-26920 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-20695](https://insights.sbomify.com/CVE-2019-20695/): Information disclosure in n/a (critical 9.4)
- [CVE-2020-14435](https://insights.sbomify.com/CVE-2020-14435/): Command injection in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-26920 is a high-severity command injection vulnerability in n/a, 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-26920 in the wild and no public exploit code.

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

## Sources

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

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