# CVE-2026-19771: Baicells EG3661M LuCI Web luci os command injection

> Remote attackers can execute arbitrary OS commands via the LuCI web interface due to improper input validation in network diagnostic parameters.

- **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/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Aug 2026
- **Updated:** 18 Aug 2026
- **Also known as:** GHSA-w9jh-6rx2-4wh5

## What is CVE-2026-19771?

CVE-2026-19771 is a high-severity command injection vulnerability in Baicells EG3661M, published on 14 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability was identified in Baicells EG3661M BaiCE_BQ6_2.0.5.3_NA. This impacts an unknown function of the file /cgi-bin/luci of the component LuCI Web Interface. Such manipulation of the argument MaxHops/Timeout/Size leads to os command injection. The attack may be launched remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-77 (Improper Neutralization of Special Elements used in a Command)

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


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

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

## Is CVE-2026-19771 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19771 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19771 is a high-severity command injection vulnerability in Baicells EG3661M, published on 14 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19771 exists.

Affected product: Baicells EG3661M. 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-19771/ (Markdown: https://insights.sbomify.com/CVE-2026-19771/index.md)
```

## Sources

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

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