# CVE-2025-12941: Denial of Service Vulnerability in NETGEAR C6220 and C6230

> Authenticated local WiFi users can reboot NETGEAR C6220 and C6230 cable modem routers, causing a denial of service.

- **Severity:** Medium 5.0 (`CVSS:4.0/AV:A/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P/AU:N/R:A/V:D/RE:L/U:Amber`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Dec 2025
- **Updated:** 9 Dec 2025
- **Also known as:** GHSA-jx7x-fxc9-2wxv

## What is CVE-2025-12941?

CVE-2025-12941 is a medium-severity missing authorization vulnerability in NETGEAR C6220, published on 9 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Denial of Service Vulnerability in NETGEAR C6220 and C6230 (DOCSIS® 3.0 Two-in-one Cable Modem + WiFi Router) allows authenticated local WiFi users reboot the router.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2025-12941?

It affects 2 products.


Products: Netgear C6220 Firmware, Netgear C6230 Firmware.

## How do I fix CVE-2025-12941?

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

## Is CVE-2025-12941 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-12941 and fix it if it is affected.

What it is: CVE-2025-12941 is a medium-severity missing authorization vulnerability in NETGEAR C6220, published on 9 Dec 2025. 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-2025-12941 in the wild and no public exploit code.

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

## Sources

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

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