● Critical · CVSS 9.8

How to Fix CVE-2026-25715: Critical Vulnerability in USR-W610

Q: Is CVE-2026-25715 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Q: Will a WAF or IDS rule fully mitigate CVE-2026-25715?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

Q: How long should I plan for the upgrade?

Typical vendor-documented upgrade windows for USR-W610 run from a few minutes to under an hour depending on cluster size. Test in a staging environment first and follow the vendor's documented HA upgrade order.

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-43879: Server-Side Request Forgery (SSRF) in AVideo — Server-Side Request Forgery (SSRF) in AVideo
How to Fix CVE-2026-3306: CWE-639 Authorization Bypass Through User-Controlled Key — CWE-639 Authorization Bypass Through User-Controlled Key
How to Fix CVE-2026-7036: Path Traversal in i9 , Path Traversal in i9
How to Fix CVE-2026-34840: oneuptime (Bundle Sibling) , oneuptime (Bundle Sibling)
How to Fix CVE-2026-6528: CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop') in Wireshark , CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop') in Wireshark

*By Sai Kiran Pandrala*

⚡ At a glance


Severity	CVSS 9.8 - Critical
Actively exploited?	Not currently listed in CISA KEV
Affected	0 <= 3.1.1.0
Fixed in	See vendor advisory
Type (CWE)	CWE-521:

What is CVE-2026-25715?

CVE-2026-25715 is a security flaw in USR-W610. The web management interface of the device allows the administrator username and password to be set to blank values. Once applied, the device permits authentication with empty credentials over the web management interface and Telnet service.

Why this CVE matters

Unpatched network-facing software is the leading initial-access vector in public breach reporting. Treat any CVSS-9 class flaw on an internet-reachable system as urgent, regardless of whether public exploit code has been observed yet.

For deployments of USR-W610 that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

USR-W610: 0 <= 3.1.1.0

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

Open USR-W610's About dialog or run the vendor-documented version-check command. Compare the result against the affected ranges in the advisory.

How to fix CVE-2026-25715

Read the vendor advisory in full: https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-050-03.json
Upgrade USR-W610 to the patched build listed in the vendor advisory.
Back up the configuration (and database, where applicable) before upgrading.
Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
Restart the affected service so the patched binary loads, then verify the new version (see verification section).

Patched-version commands

Vendor advisory: https://www.cisa.gov/news-events/ics-advisories/icsa-26-050-03

Affected: USR-W610: 0 <= 3.1.1.0

Patched in: 3.1.1.0


# Vendor advisory: https://www.cisa.gov/news-events/ics-advisories/icsa-26-050-03

# npm / Yarn / pnpm.
npm install usr-w610@3.1.1.0
npm ls usr-w610

# Python / pip.
python -m pip install --upgrade "usr-w610>=3.1.1.0"
python -m pip show usr-w610

# Container image.
docker pull <your-registry>/usr-w610:3.1.1.0
docker stop usr-w610 && docker rm usr-w610
docker run -d --name usr-w610 <your-registry>/usr-w610:3.1.1.0


# Vendor advisory: https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-050-03.json
# Same flow from a Windows admin workstation.
npm install usr-w610@3.1.1.0
docker pull <your-registry>/usr-w610:3.1.1.0

Verify the fix landed


# Vendor advisory: https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-050-03.json
# Post-patch verification (replace <service> with the real service unit).
journalctl -u <service> --since "10 minutes ago"
dmesg --since "10 minutes ago"

# Re-scan with your vulnerability scanner (Nessus, Qualys, Tenable, OpenVAS).
# It should no longer flag CVE-2026-25715 on the patched target.

If you cannot patch immediately

Restrict access to the management interface to trusted internal IP addresses only. Block public access at the firewall and require VPN for any remote administration. Apply the patch as soon as a maintenance window allows.

How to verify the fix worked

After applying the patch, verify the running version in the product's admin UI or via the vendor-documented CLI command.
Confirm the patched build matches the version listed in the vendor advisory.
Run an authenticated vulnerability scan with a current signature set and confirm the scanner no longer flags CVE-2026-25715.
Review logs for the entire pre-patch window for indicators of compromise listed in the vendor or CISA advisory.
Confirm any network-layer mitigations that were applied as a stopgap have been reverted (or left in place intentionally) once the patch is verified.

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for log entries that do not match your normal request patterns, especially repeated requests to the same uncommon endpoint, and any administrative changes you cannot tie back to a known operator.

Frequently asked questions

Is CVE-2026-25715 being exploited in the wild?