Skip to content
IoT

CVE-2026-41922

9.3
Critical
EPSS 5%May 5, 2026

Unauthenticated OS command injection in WDR201A WiFi Extender enables remote RCE.

common questions

Is CVE-2026-41922 being exploited?

Not confirmed. CVE-2026-41922 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 5.0% probability of exploitation in the next 30 days.

How severe is CVE-2026-41922?

CVE-2026-41922 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-41922?

Not known from our data. No patch reference has been recorded for CVE-2026-41922, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-41922 affect?

CVE-2026-41922 affects WDR201A WiFi Extender HW V2.1 (FW LFMZX28040922V1.02). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-41922?

Apply firmware patch when available; restrict management UI access.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
WDR201A WiFi Extender HW V2.1 (FW LFMZX28040922V1.02)
impact

Remote code execution via OS command injection; unauthenticated access allows full control of the device.

action required

Immediate action required

affected versions
Shenzhen Yipu Commercial and Trading Co., Ltd WDR201A WiFi Extender
  • affected<= 1.02.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free