# CVE-2020-26919: Netgear JGS516PE Devices Missing Function Level Access Control

> Attackers can bypass function-level access controls on NETGEAR JGS516PE switches to perform unauthorized actions.

- **Severity:** Critical 9.8 (`CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:N`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Oct 2020
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-cwxx-ph2v-87p8

## What is CVE-2020-26919?

CVE-2020-26919 is a critical missing authorization vulnerability in n/a, published on 9 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NETGEAR JGS516PE devices before 2.6.0.43 are affected by lack of access control at the function level.

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

It affects 1 product.


Products: Netgear Jgs516pe Firmware.

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

No fix has been published for CVE-2020-26919 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.

## Is CVE-2020-26919 being exploited?

Yes. Attackers have exploited CVE-2020-26919 in the wild since at least 3 Nov 2021.

Public exploit code:

- NETGEAR ProSAFE Plus - Unauthenticated Remote Code Execution (nuclei): http/cves/2020/CVE-2020-26919.yaml

## Other vulnerabilities in n/a

- [CVE-2020-11791](https://insights.sbomify.com/CVE-2020-11791/): Cross-site scripting in n/a (medium 5.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-26919 is a critical missing authorization vulnerability in n/a, published on 9 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2020-26919 in the wild since at least 3 Nov 2021.

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-26919/ (Markdown: https://insights.sbomify.com/CVE-2020-26919/index.md)
```

## Sources

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

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