# CVE-2020-26921: Auth bypass in n/a

> Attackers can bypass authentication on specific NETGEAR managed switches to gain unauthorized access to the device interface.

- **Severity:** High 8.3 (`CVSS:3.1/AC:L/AV:A/A:H/C:L/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-9p3v-vg9h-wqg7

## What is CVE-2020-26921?

CVE-2020-26921 is a high-severity authentication bypass 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 authentication bypass. This affects GS110EMX before 1.0.1.7, GS810EMX before 1.7.1.3, XS512EM before 1.0.1.3, and XS724EM before 1.0.1.3.

Weakness: CWE-287 (Improper Authentication)

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

It affects 4 products.


Products: Netgear Gs110emx Firmware, Netgear Gs810emx Firmware, Netgear Xs512em Firmware, Netgear Xs724em Firmware.

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

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

## Is CVE-2020-26921 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-21122](https://insights.sbomify.com/CVE-2018-21122/): Denial of service in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-26921 is a high-severity authentication bypass 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-26921 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-26921/ (Markdown: https://insights.sbomify.com/CVE-2020-26921/index.md)
```

## Sources

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

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