# CVE-2025-25246: Code injection in XR1000

> Unauthenticated remote attackers can execute arbitrary code on NETGEAR XR1000, XR1000v2, and XR500 routers.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Feb 2025
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-4qgw-f8fj-66qh

## What is CVE-2025-25246?

CVE-2025-25246 is a high-severity code injection vulnerability in NETGEAR XR1000, published on 5 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NETGEAR XR1000 before 1.0.0.74, XR1000v2 before 1.1.0.22, and XR500 before 2.3.2.134 allow remote code execution by unauthenticated users.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2025-25246 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-25246 is a high-severity code injection vulnerability in NETGEAR XR1000, published on 5 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-25246 in the wild and no public exploit code.

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

## Sources

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

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