Skip to content
IoT

CVE-2026-20892

8.6
High
EPSS 0.57%Mar 11, 2026

Code injection enables admin to execute arbitrary commands on affected devices.

common questions

Is CVE-2026-20892 being exploited?

Not confirmed. CVE-2026-20892 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 0.57% probability of exploitation in the next 30 days.

How severe is CVE-2026-20892?

CVE-2026-20892 is rated High with a CVSS score of 8.6. 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-20892?

Not known from our data. No patch reference has been recorded for CVE-2026-20892, 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-20892 affect?

CVE-2026-20892 affects MR-GM5L-S1, MR-GM5A-L1. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-20892?

Patch when released; enforce least-privilege admin access.

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

executive summary
technical analysis
affected
MR-GM5L-S1MR-GM5A-L1
impact

Admin-accessible code injection allows executing arbitrary commands, potentially full device takeover.

action required

Patch when possible

affected versions
Micro Research Ltd. MR-GM5A-L1
  • affectedfirmware versions prior to v2.01.04N1_02
Micro Research Ltd. MR-GM5L-S1
  • affectedfirmware versions prior to v2.01.04N1_02

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