# CVE-2026-20892: Code injection in MR-GM5A-L1

> Administrative users can execute arbitrary commands on Micro Research MR-GM5L-S1 and MR-GM5A-L1 devices due to a code injection flaw.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Mar 2026
- **Updated:** 11 Mar 2026
- **Also known as:** GHSA-8cjp-9cg5-vcjh

## What is CVE-2026-20892?

CVE-2026-20892 is a high-severity code injection vulnerability in Micro Research Ltd. MR-GM5A-L1, published on 11 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Code injection vulnerability exists in MR-GM5L-S1 and MR-GM5A-L1, which may allow an attacker with administrative privileges to execute arbitrary commands.

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

## Which versions are affected by CVE-2026-20892?


## How do I fix CVE-2026-20892?

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

## Is CVE-2026-20892 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-20892 and fix it if it is affected.

What it is: CVE-2026-20892 is a high-severity code injection vulnerability in Micro Research Ltd. MR-GM5A-L1, published on 11 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-20892 in the wild and no public exploit code.

Affected product: Micro Research Ltd. MR-GM5A-L1. 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-2026-20892/ (Markdown: https://insights.sbomify.com/CVE-2026-20892/index.md)
```

## Sources

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

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