Unauthenticated remote code execution in NETGEAR XR1000, XR1000v2, and XR500 routers

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2025-25246?

CVE-2025-25246 is a vulnerability classified as Improper Control of Generation of Code, affecting XR1000 (affected versions: < 1.0.0.74), XR1000v2 (affected versions: < 1.1.0.22), and XR500 (affected versions: < 2.3.2.134). This vulnerability is rated High, with a CVSS score of 8.1. Current sources do not report this vulnerability as exploited.

Overview

Original source data

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.

Affected products and scope

The confirmed affected and fixed boundaries are:

  • NETGEAR XR1000: versions less than 1.0.0.74 are affected; NETGEAR identifies 1.0.0.74 as fixed.
  • NETGEAR XR1000v2: versions less than 1.1.0.22 are affected; NETGEAR identifies 1.1.0.22 as fixed.
  • NETGEAR XR500: versions less than 2.3.2.134 are affected; NETGEAR identifies 2.3.2.134 as fixed.

The CNA record sets default_status to unaffected outside each declared affected range. No additional product or firmware branch is confirmed by the available evidence.

Technical details

The CNA classifies the weakness as CWE-94, Improper Control of Generation of Code, also known as Code Injection. An unauthenticated user can reach the flaw over the network and achieve remote code execution; the record also states that user interaction is not required and characterizes attack complexity as high. The attacker-controlled input, endpoint, parameter, service, parser, and vulnerable code path are not disclosed. The specific firmware component is unknown, so the available evidence does not establish whether the flaw is in an HTTP service, API, daemon, or other subsystem. The affected scope is limited to the models and firmware branches listed in affected_summary; no other products are confirmed affected.

Exploitability

The flaw is network reachable, can be used by an unauthenticated user, and does not require a legitimate user to perform an action. The record characterizes attack complexity as high, so exploitation is not described as automatic or straightforward merely because network access is available. No public exploit is identified in the supplied record, and the returned enrichment recorded exploitation as none at its assessment time. No exploit code, campaign, victim, or specific IOC is named. This does not establish that exploitation will not occur in the future.

Technical impact

Successful exploitation results in remote code execution on an affected router. The record establishes that authentication and user interaction are not required, but it does not state whether execution has administrator, root, or sandboxed privileges, nor does it describe persistence after reboot. The recorded impact dimensions indicate possible compromise of confidentiality, integrity, and availability, while scope is characterized as unchanged. Realistic consequences may include unauthorized router changes, service loss, or effects on data and traffic passing through the device, but these are possible outcomes rather than a confirmed breach. No specific victim, campaign, or incident is identified.

Business impact

If exploitation succeeds, an attacker may execute code on the affected router and potentially alter the device's behavior or configuration. Because routers are network infrastructure, compromise could cause connectivity disruption, weaken trust in traffic, or affect networks that depend on the device. The record indicates high potential impact to confidentiality, integrity, and availability, but it does not describe a confirmed incident or specific organization. No breach, campaign, or victim is named, so the actual organizational effect remains environment-dependent.

Remediation

  1. Upgrade NETGEAR XR1000 to firmware 1.0.0.74.
  2. Upgrade NETGEAR XR1000v2 to firmware 1.1.0.22.
  3. Upgrade NETGEAR XR500 to firmware 2.3.2.134.
  4. After updating, verify the model and installed firmware on each device. NETGEAR recommends downloading firmware through its support channel and following the applicable user manual, release notes, or product support instructions.
  5. If the installed firmware cannot be confirmed, treat the device as potentially affected until the check is complete. The record and advisory do not document a separate compensating mitigation in place of updating the firmware.

Detection

  1. Inventory NETGEAR XR1000, XR1000v2, and XR500 routers in the environment, including the exact model and installed firmware.
  2. Compare each firmware version with the affected boundaries and corresponding fixed releases listed in affected_summary and remediation.
  3. Review firmware deployment records and confirm that the update completed on each device, rather than relying only on the firmware package having been downloaded.
  4. Review whether the routers are reachable from untrusted network paths as a precaution, because the flaw is network reachable.
  5. NETGEAR does not publish a specific endpoint, log event, or IOC for this flaw. Therefore, the absence of a matching log entry does not prove that a device is safe; generic network monitoring should be treated as an additional precaution, not a known indicator.
Sources (8)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.